-
Notifications
You must be signed in to change notification settings - Fork 53
v0.5.0 broke chruby compatibility when lunching from CLI #168
Comments
@steelbrain Looks like this is a |
@pecigonzalo Can you tell us your OS, shell and the env variables in question? |
Archlinux, ZSH (with zplug). I tried looking at the code, but tbh i dont know much about atom plug deployment or how are you importing the envs, so i couldnt figure out what is different. |
Can you do |
Unfortunately my laptop if out of juice at the moment and i dont have the adapter with me (the device i initially tested with). |
I wanted to chime in on this issue as well. I'm seeing the same thing. macOS 10.12 with ZSH (oh-my-zsh). $ echo $GEM_HOME
/Users/<username>/.gem/ruby/2.3.1 $ process.env.GEM_HOME
undefined If I launch Atom from the command line, then EDIT: Looks like I read this wrong. My environment variables load correctly when launched from CLI, but not when launched through a GUI method. You can ignore my comment. |
As agreed: GEM_HOMEShell
Atom console
GEM_PATHShell
Atom console
Error
and
|
@goronfreeman Yes Mac apps have that issue. Therefore we fix it with @pecigonzalo Thanks that was very helpful, can you show the output of |
|
@steelbrain When launching from the GUI, that command outputs |
I use zplug too and have a similar issue with v0.5.0, when it runs linter-rubocop, I encounter the following error:
Either of the above two fixes the problem. OS: OS X 10.11.6 |
After some further investigation, I've found that the problem in the above comment is occurs only when I use a specific plugin (in my case, that is emoji-cli) via zplug. Although I still don't know why the problem occurs only after upgrading linter-rubocop v0.5.0, either I'm not sure if other plugins rather than emoji-cli also cause errors, maybe I should investigate emoji-cli for the moment. |
@5t111111 I can confirm that this issue still exists with |
On version 0.4.7 lunching Atom from the CLI allowed it to use the CLI path/env variables.
These seems to be broken on 0.5.0
The text was updated successfully, but these errors were encountered: