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@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@lists.macromates.com https://lists.macromates.com/listinfo/textmate

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).

OK, I fixed it by navigating to /Library/Application Support/TextMate/Ruby/1.8.7/bin in the Finder, clicking on the ruby executable, and then telling the system it was OK to open it, like you do with an unsigned app. A bit crummy, but it seems to have worked.

I expect disabling Gatekeeper would have worked too, but I don’t like to do that.

I don’t know why this happened – it may just be my setup and its history – but I’m posting this in case anyone else has the same problem.

On 28 Nov 2019, at 1:13, Nigel Chapman wrote:

OK, I fixed it by navigating to /Library/Application Support/TextMate/Ruby/1.8.7/bin in the Finder, clicking on the ruby executable, and then telling the system it was OK to open it, like you do with an unsigned app. A bit crummy, but it seems to have worked.

I expect disabling Gatekeeper would have worked too, but I don’t like to do that.

I don’t know why this happened – it may just be my setup and its history – but I’m posting this in case anyone else has the same problem.

I *think* it may have been because you moved the file from an old machine to a new one and somehow it got quarantined in the process and thus needed to be manually OK’ed.