TextMate December 2021

textmate@lists.macromates.com

18 participants
6 discussions

Re: TextMate fails to compile with Xcode 13.1

by Kevin Sjöberg

I’m seeing the same thing. Just tried to compile TextMate under Xcode 13.1, on macOS 12.0.1, and got the exact same error. Allan have you bumped into this yourself yet? Thanks, Kevin

3 years

Universal build incompatible with Bundle Support binaries

by christos＠mac.com

I just upgraded to 2.0.17 and now any bundle that uses pre-compiled binaries in Bundle Support bundle fails to load due to the incompatible architectures: > /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require': dlopen(/Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle, 9): no suitable image found. Did find: (LoadError) > /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle: no matching architecture in universal wrapper > /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle: no matching architecture in universal wrapper - /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle > from /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' > from /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/textmate.rb:4:in `<top (required)>' > from /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' > from /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' > from /Users/christos/Library/Application Support/TextMate/Bundles/Linter.tmbundle/Support/lib/linter.rb:1:in `<top (required)>' > from /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' > from /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' > from Lint/Strip/Ensure on Save:2:in `<main>' I checked and the builds don't contain arm_64 architectures: > [~]> file "/Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle" > /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle: Mach-O universal binary with 3 architectures: [ppc_7400:Mach-O bundle ppc_7400] [i386:Mach-O bundle i386] [x86_64:Mach-O 64-bit bundle x86_64] > /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle (for architecture ppc7400): Mach-O bundle ppc_7400 > /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle (for architecture i386): Mach-O bundle i386 > /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle (for architecture x86_64): Mach-O 64-bit bundle x86_64 I can't even find the source for those binaries to try and build them. Any ideas?

3 years

TM not reopening after a reboot

by Walter Lee Davis

TextMate 2.0.23 on Mac OS 12.1 has recently (last few restarts) not re-opening with all my other apps after login. I have not changed any preferences in this area, and all the other apps that were open before restart seem to come back just fine, but TM requires that I click the Dock icon instead. All my previous documents (saved and unsaved) are opened as I would expect, it's just the app itself that doesn't seem to want to start up. Are there any preferences I could fiddle around this? Anything that might have become corrupted that I could jostle awake somehow? Thanks in advance, Walter

3 years

I love TM2, but when changing tabs, the scrolling misbehaves

by forum＠josh.ch

Hey everybody I've been a TM user since the very early days. I had a license for TM1, and I kept using TM2 through all these years while many fellow devs switched to fancy coding IDEs. I love the simplicity of TM2, and it does just what I want it to do, nothing more. But since a while, I experience that TM2 has some scrolling issues. When I switch between the tabs (opened text files), the scrolling jumps quite unpredictably. I always have to move the cursor (arrow key), so the current line is in the viewport again. This is annoying, and for the first time in my life I'm tempted to abandon TM2 and move to some other simple editor. Can anyone tell me whether there is a way to fix this? Or that it will be fixed soon? Thanks a log Josua

3 years, 1 month

Textmate 2.0.23 on Monterey on M1

by Christophe VG

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: 1. 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). 2. 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

3 years, 2 months

Where did you go, Allan?

by mail＠kevinsjoberg.com

Previously, I enjoyed the small chitchats and conversations we've had in the Freenode IRC channel. Then the Freenode fiasco happened. We're now a small bunch in the Libera.Chat #textmate channel, and I'd love if we could get the community back together. For instance, I miss hearing about what you're up to, Allan. Thanks, Kevin

3 years, 2 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

TextMate December 2021