3 ms·
But foo is more likely to jump around than env, right? I'd like someone else to make up my mind on this. Please discredit the env approach in any way possible
by frou_dh 16y ago
But foo is more likely to jump around than env, right?
I'd like someone else to make up my mind on this. Please discredit the env approach in any way possible :-)
- glenngillen 16y agoWould love some more discussion on this too, to discredit either approach. I've gone with the env approach precisely because I've found the only other ways I know to be even more brittle.
- jamesbritt 16y agoSince using RVM on multiple machines I've found I cannot assume a fixed, universal path to the ruby interpreter, so env is the choice for me. I've also never had an issue with env itself not being where I expect it, but if I ever do I think a symlink addition would solve the problem.