Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note about running Atom in cli vs. icon #26

Open
rgbkrk opened this issue Mar 4, 2014 · 3 comments
Open

Add note about running Atom in cli vs. icon #26

rgbkrk opened this issue Mar 4, 2014 · 3 comments

Comments

@rgbkrk
Copy link
Contributor

rgbkrk commented Mar 4, 2014

As surfaced in atom-community/atom-script#5 (comment), running Atom via the icon/Applications will load the environment used by launchctl rather than your shell.

Running Atom from the terminal is the way to go if you want access to virtualenv, rvm, nvm, etc.

@jbranchaud
Copy link
Owner

Interesting. Any thoughts on a way to configure Atom to launch with your preferred environment from the icon?

@rgbkrk
Copy link
Contributor Author

rgbkrk commented Mar 5, 2014

It kind of makes me wonder if it should be part of the ~/.atom setup. That way when atom comes out for Windows, you've got what you need setup.

The only suggestion I would have for people is to mirror env vars they want into ~/.launchd.conf, which follows a setenv format:

setenv KEY 'value'

For script we'll be adding a way to set up the env you need on run. Right now it defaults to using process.env.

@tresni
Copy link

tresni commented Mar 13, 2014

I am using the init script idea from #62 and it works beautifully from me. launchd.conf and everything else people suggest just didn't seam to work for me on Mavericks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants