search

shdqcdsn / counterclockwise

Automatically exported from code.google.com/p/counterclockwise
0 stars 0 forks source link

Path issue? #668

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
https://groups.google.com/d/msg/clojuredev-users/IRGBCeivySo/HsIUidwr3WcJ

Original issue reported on code.google.com by laurent....@gmail.com on 6 Nov 2014 at 11:55

GoogleCodeExporter commented 9 years ago 
Fix idea: detect that we're on OS X, and if it's the case, then grab the PATH 
environment variable that will be set, then append to it /bin , /usr/bin, 
/usr/local/bin if they're not already there

Original comment by laurent....@gmail.com on 4 Dec 2014 at 3:24

GoogleCodeExporter commented 9 years ago 
How are you planning to "grab the PATH environment variable"? Given that PATH 
can be set in multiple places, the only reliable way I can think to do this is 
to fork a login shell?

Original comment by p...@paulbutcher.com on 4 Dec 2014 at 3:35

GoogleCodeExporter commented 9 years ago 
By default, the processes started via the Eclipse launch mechanism can 
propagate the environment variables Eclipse itself was started with. That's how 
leiningen launcher is configured itself.

I remember this is pluggable: I may be able to override the method that returns 
the environment variables to pass to leiningen, check if the usual suspects are 
missing in the PATH variable (or if the PATH variable itself is totally 
missing), and hopefully fix 99% of the cases by adding /usr/local/bin, 
/usr/bin, /bin. In your case, it's /usr/local/bin that's missing.

Original comment by laurent....@gmail.com on 4 Dec 2014 at 3:43

GoogleCodeExporter commented 9 years ago 
So I will not really "grab the PATH variable", just intercept and enhance the 
one Eclipse has been started with.

No messing with bash / zsh / tsch / ...

Original comment by laurent....@gmail.com on 4 Dec 2014 at 3:44