[TxMt] Re: Problem running ruby commands

[Nigel Chapman]

Matt,

Thanks for your suggestion. Sadly it did not avail.

I now have /usr/local/bin at the beginning of the PATH, with the Textmate bundle support binary right at the end, but, presumably because the commands that are giving me trouble specify ruby18, I still can’t get them to run.

I’m just hoping there is some magic that will persuade MacOS to trust the embedded Ruby 18, but so far all it offers to do is move it to the bin (as the trash is now called in UK English after all these years).


> On 25 Nov 2019, at 18:54, Matt Neuburg <matt at tidbits.com> wrote:
> 
> Insert Color works fine for me. I find that the order in which your PATH is defined is crucial. My order is my `.rbenv` ruby followed immediately by the default $PATH followed by everything else. If the default $PATH is listed in the wrong spot, I get issues similar to what you've described. However, I'm still back at 2.0-rc.10, for reasons I've already explained, so that might matter too. m. 
> 
> --
> matt neuburg, phd = http://www.apeth.net/matt/
> pantes anthropoi tou eidenai oregontai phusei
> Programming iOS 13! http://shop.oreilly.com/product/0636920310075.do
> iOS 13 Fundamentals! http://shop.oreilly.com/product/0636920310068.do
> RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
> 
>> On Nov 26, 2019, at 4:23 AM, Nigel Chapman <nigelchap at icloud.com> wrote:
>> 
>> I have encountered a problem running bundle commands that are implemented as ruby scripts with a shebang line
>> 
>> #!/usr/bin/env ruby18
>> 
>> I get an alert like this:
>> 
>> <Screenshot 2019-11-25 at 15.19.12.png>
>> 
>> 
>> Here I was trying to use Insert Color… from the CSS bundle, but the same thing happens with other commands, including from bundles I made myself.
>> 
>> I am pretty sure that this only started when I upgraded to Catalina. (Presently on 10.15.1, TM 2.0.3. It doesn’t happen with 2.0.3 running on another machine with High Sierra.) Possibly this is related to the problem of loading plug-ins that was fixed in 2.0.1.
>> 
>> If I change the shebang to point to the version of ruby I installed with Homebrew commands work fine, but I don’t much want to edit every command in every bundle.
>> 
>> Has anybody else seen this? Do you know of any workrounds?
>> 
>> 
>> 
>> _______________________________________________
>> TextMate mailing list
>> TextMate at lists.macromates.com
>> https://lists.macromates.com/listinfo/textmate
> 
> 
> _______________________________________________
> TextMate mailing list
> TextMate at lists.macromates.com
> https://lists.macromates.com/listinfo/textmate