layout | title |
---|---|
page |
Frequently Asked Questions |
An extension to the official FAQ.
There are a few ways to get an invite.
- Invites can be requested on http://www.atom.io by entering your email address. However, it may take some time to receive your invite
- The first users get 3 invites that they can give to friends. So ask friends with invites for one.
- Hang out on Twitter, IRC, or other social networks. Many people are willing to give out invites.
Atom: ##atom
Invites: ##atom-invitations
The official Atom FAQ says,
We have not finalized licensing on Atom's core (nucleus?), but we're aiming for a common ground between fully-closed and fully-open.
And then goes on to assure that any non-core packages that are developed by GitHub will be released under the MIT license.
There is some earlier discussion around this question from the Atom discourse page in which Mojombo (or Tom if you prefer) responds:
Atom won't be closed source, but it won't be open source either. It will be somewhere inbetween, making it easy for us to charge for Atom while still making the source available under a restrictive license so you can see how everything works. We haven't finalized exactly how this will work yet. We will have full details ready for the official launch.
In response to a follow-up question, Mojombo goes on to affirm that, yes, anyone will be able to submit pull requests to Atom core.
Atom will be competitively priced compared to similar editors, which typically range between $30 and $100.
See TechStack.md
Not any time soon. The Atom team is focusing on fixing bugs and having a Mac-only beta.
Using CoffeeScript and CSON is a matter of preference and readability as well as compatibility with EC6.
JavaScript and JSON can be used in Atom packages, there is no requirement to write a single line of CoffeeScript or CSON to make an Atom package.
In Atom any .coffee
/.cson
/.less
files can always be .js
/.json
/.css
files instead.
Both the metrics and exception-reporting packages store a userId
value
in the config.cson
file. Neither of these reveal sensitive data, so you can
feel free to commit your config.cson
file as part of your
dotfiles configuration.
metrics source, exception-reporting source
For now, this isn't supported. Each Atom window seems to be dedicated to a single directory.
In the meantime, there is a workaround that involves using symbolic links.
Do you know of another solution or workaround? Open an issue and tell us about it.