Running Node.js? about atom-script HOT 11 CLOSED

Think you're hitting the same problem as #61. Try opening atom from your terminal and not the icon.

from atom-script.

Wow, that's crazy. Yup. Totally the problem. Thanks! So that's something Atom core has to fix?

from atom-script.

Well, it's more a consequence of how environment variables work on a Mac. I'm not sure that there's much that Atom could do about it, even.

from atom-script.

I see. I was reading more into the other issue and it makes a little more sense though if I were to change my init on Atom, what would it need to be? How can I pick up my environment variables? ...So that I could run atom using launcher... Not that I don't have a million terminal windows open at any given time, but I'll get annoyed when I forget and launch from launcher and then have to reopen projects all over again because Atom doesn't save your state like Sublime.

from atom-script.

How can I pick up my environment variables?

You can use launchctl setenv to customize your PATH for Atom (or anything else you launch from the bar).

There is a clever trick on StackOverflow for keeping the two in sync, but I can't vouch for it personally (I just launch from terminal everywhere by habit).

from atom-script.

There is always setting process.env in your init script for Atom too:

from atom-script.

Can you pick up your user variables from here too? Or do I need to maintain a separate list?

from atom-script.

As in what you define in your .bashrc or .bash_profile?

from atom-script.

Yup

from atom-script.

This did not work for me; any updates on what to do?

from atom-script.

@intothev01d that worked; thx. Why is there a difference?

from atom-script.