FWIW I use an M1 and an iMac Pro and have no issues. I have it set to check for updates daily and install latest things. You might suffer if you have an older version of TextMate?
On Nov 23, 2021, at 12:15, Walter Lee Davis via TextMate textmate@lists.macromates.com wrote:
I recently migrated to a new M1 Max Mac, and have not had any issue with TM2 and the ⌘/ (toggle escape) shortcut. System Ruby is 2.6.8, and I use RVM and run whatever my Rails project needs with that. I believe there may be a version of Ruby bundled into TextMate just for the purpose of running these older command packages, but I have never had an issue and never needed to dig into it at all.
Walter
On Nov 22, 2021, at 4:59 PM, Christophe VG via TextMate textmate@lists.macromates.com wrote:
Hi,
After many grateful years with Textmate on my Macs, I also installed it on my new MBP with M1 CPU, running Monterey. Everything seems to run smooth until I hit cmd+/ to toggle/comment a region ;-)
What I think I’ve learned is that:
- Monterey doesn’t ship a 1.8 ruby version anymore (at /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby where the bundle-support bundle’s ruby18 shim looks for it).
- The “downloaded” 1.8.7 version (from https://archive.textmate.org/ruby/ruby_1.8.7.tbz at ~/Library/Application\ Support/TextMate/Ruby/1.8.7/bin/ruby isn’t compatible with the M1 arch).
So the error is pretty “correct” :
/Users/.../Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/bin/ruby18: line 43: /Users/.../Library/Application Support/TextMate/Ruby/1.8.7/bin/ruby: Bad CPU type in executable /Users/.../Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/bin/ruby18: line 43: /Users/.../Library/Application Support/TextMate/Ruby/1.8.7/bin/ruby: Undefined error: 0
To get around it (for now) I first tried to install a 1.8 version of ruby using rbenv, which didn’t succeed - quick guess it isn’t supported in any way anymore ?! ;-)
So I resorted to adding a prefix to the $PATH variable pointing to ~/bin and adding a small shell script there pointing to a 2.x version
% cat ~/bin/ruby18 #!/bin/bash RBENV_VERSION=2.7.4 ruby "$@“
So that “resolved” my urgent need ;-) Once I get into areas/bundles with ruby18 code that doesn’t play nice with ruby 2.x (IANARubyKnowledgeablePersonSorry) I’ll probably bump into a new set of issues - fingers crossed for my limited Bundle needs ;-)
Is there anything I can look into to help out here? Or have I simply missed the obviously better approach to solve this?
Thanks and regards, Christophe
TextMate mailing list -- textmate@lists.macromates.com To unsubscribe send an email to textmate-leave@lists.macromates.com
TextMate mailing list -- textmate@lists.macromates.com To unsubscribe send an email to textmate-leave@lists.macromates.com