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
The environment variables that gs sets are overwritten by the profile/startup file of the shell it fires up.
This renders gs quite useless when using a tool like rbenv, which does it set up in the profile/startup file of the shell. This file is executed after gs set $PATH, which makes it look something like ~/.rbenv/shims/:~/.rbenv/bin:./gs/bin. This makes it impossible to run executables from gs' gemset that are also installed globally.
The text was updated successfully, but these errors were encountered:
Hmm, I see what you mean, but it doesn't work like that for me... I get ./gs/bin followed by ~/.rbenv/shims:~/.rbenv/bin in the subshell. rbenv 0.3.0 .
@ericgj I'm thinking that it's more a problem with rbenv. As suggested in #6, maybe the best way to deal with this would be to report the issue to the rbenv guys. Let me know if you do it so I can chip in.
The environment variables that gs sets are overwritten by the profile/startup file of the shell it fires up.
This renders gs quite useless when using a tool like rbenv, which does it set up in the profile/startup file of the shell. This file is executed after gs set $PATH, which makes it look something like
~/.rbenv/shims/:~/.rbenv/bin:./gs/bin
. This makes it impossible to run executables from gs' gemset that are also installed globally.The text was updated successfully, but these errors were encountered: