You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#75 (comment) provided advice to start atom from an nvm-configured shell in order to get the correct $PATH.
An alternative is to capture the $PATH from a shell after being configured by nvm, and use that for process.env.PATH. Adding this to my init.coffee allows me to start Atom per usual from the e.g. ubuntu dock, but still have atom-ide-purescript pick up the installed executables it needs:
#75 (comment) provided advice to start
atom
from annvm
-configured shell in order to get the correct$PATH
.An alternative is to capture the
$PATH
from a shell after being configured bynvm
, and use that forprocess.env.PATH
. Adding this to myinit.coffee
allows me to start Atom per usual from the e.g. ubuntu dock, but still have atom-ide-purescript pick up the installed executables it needs:I don't know if that's something that can be safely added to an Atom plugin (probably not), but perhaps might be worth a README / wiki addition.
Thanks for the great plugin! 😄
The text was updated successfully, but these errors were encountered: