The todo bundle triggers this message: Failure running "Insert TODO List". env: ruby18: No such file or directory
When I run ruby -v, I get ruby 2.0.0p451 (2014-02-24 revision 45167) [universal.x86_64-darwin13]
I'm on TextMate 9547 and Os 10.9.3
Do I switch paths to get to ruby 1.8?
Thanks for any advice. --Gildas
On 23 Jun 2014, at 20:17, Gildas Hamel wrote:
[…] env: ruby18: No such file or directory […] Do I switch paths to get to ruby 1.8?
If you change PATH in Preferences → Variables or ~/.tm_properties then you MUST extend the existing PATH (rather than replace it), e.g.:
PATH = $PATH:/usr/local/bin
On 23 Jun 2014, at 20:39, Allan Odgaard wrote:
On 23 Jun 2014, at 20:17, Gildas Hamel wrote:
[…] env: ruby18: No such file or directory […] Do I switch paths to get to ruby 1.8?
If you change PATH in Preferences → Variables or ~/.tm_properties then you MUST extend the existing PATH (rather than replace it), e.g.:
PATH = $PATH:/usr/local/bin
Here is my PATH. Is there anything I should change?
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/texbin:/usr/X11/bin:/usr/texbin:/opt/local/bin:/opt/local/sbin:
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 23 Jun 2014, at 22:14, Gildas Hamel wrote:
On 23 Jun 2014, at 20:39, Allan Odgaard wrote:
If you change PATH in Preferences → Variables or ~/.tm_properties then you MUST extend the existing PATH (rather than replace it), e.g.:
PATH = $PATH:/usr/local/bin
Here is my PATH. Is there anything I should change?
Yes, as said, you MUST change how you set PATH to append to $PATH rather than specify the entire value.
I don’t know what locations you actually require (in addition to the default locations), but this should work for most users:
$PATH:/usr/texbin:/usr/local/bin:/opt/local/bin
The 3 additional locations added here are tex, homebrew (and most custom installers), plus MacPorts.
Allan,
Same things hit me (my extraneous ruby18 bug report). I think it would be reasonable do append bundle support path at the end of user's PATH instead of setting implicit PATH extension requirement.
Regards,
On 23 Jun 2014, at 22:56, Adam Strzelecki wrote:
Same things hit me (my extraneous ruby18 bug report). I think it would be reasonable do append bundle support path at the end of user's PATH instead of setting implicit PATH extension requirement.
I was surprised about how many people ran into problems because of this change, so it’s definitely food for thought.
That said, we have had users in the past altering their PATH in a way that broke TextMate (unrelated to the recent change), so I’m leaning more toward sort of a “settings doctor” that can check that the environment is not incorrectly setup, which would include checking that the mandatory bundles are there, etc..
That said, we have had users in the past altering their PATH in a way that broke TextMate (unrelated to the recent change), so I’m leaning more toward sort of a “settings doctor” that can check that the environment is not incorrectly setup, which would include checking that the mandatory bundles are there, etc..
I think a “settings doctor” would be great! (I really like Homebrew’s `brew doctor` for example, it has already proven so helpful on many occassions).
Stefan
On 23/06/2014 19:39, Allan Odgaard wrote:
On 23 Jun 2014, at 20:17, Gildas Hamel wrote:
[…] env: ruby18: No such file or directory […] Do I switch paths to get to ruby 1.8?
If you change PATH in Preferences → Variables or ~/.tm_properties then you MUST extend the existing PATH (rather than replace it), e.g.:
PATH = $PATH:/usr/local/bin
Hi,
I'm seeing the same issue with the latex bundle.
I haven't changed my settings, I don't think. Has something changed in textmate to make this happen?
Andrew
-
Adam Strzelecki -
Allan Odgaard -
Andrew Jaffe -
Gildas Hamel -
Stefan Daschek