TextMate March 2021

textmate@lists.macromates.com

14 participants
16 discussions

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?

2 years, 2 months

Find in Files display bug

by Jonathan Monahan

Hi, Firstly, Allan et al, thank you for everything you do. We’ve been using TextMate 1 and then 2 for years at my company. Recently a bug has cropped up in the Find in Files list, for example: I haven’t worked out what causes it, but parts of the previous searches are left in the list and overlay subsequent searches. A restart clears it obviously, but nothing else - the fragments just linger and accumulate making it gradually more and more difficult to see the results. I’m on 2.0.19 on Big Sur. I’m guessing that the bug started occurring around version 2.0.16. There seem to have been quite a few changes in the Find dialog in version 2.0.16. Regards, Jonathan.

3 years

Files open as new tab with existing untitled windows. Is there an option to force new files to open in a new window?

by Quinn Comendant

Anyone can help here? Sorry if this has been asked before, I searched and didn't find anything related. I have the habit of keeping several untitled windows open with bits of text or notes. Right now I have 3 untitled windows, all minimized in the Dock. If I open an arbitrary file, it will open it as a tab in one of these untitled windows. This includes files that belong to a project in a folder containing a .tm_properties file. I find this pretty annoying, because these files end up grouped with the untitled document that contains something totally unrelated. When I close the tab that opens, I have to minimize the untitled document again. Is there a way to force Textmate to always open files in either a window corresponding to their project, or otherwise just a new window? Thanks! Quinn

3 years, 1 month

Minor graphical bugs

by Jacob Carlborg

I’ve noticed there are some minor graphical bugs in TextMate. I think most of these bugs are new in Big Sur. * The icon in the toolbar (or whatever it’s called) above the file browser could use some left margin: * The selection for the tab buttons in the About window are a bit off: * The text in the completion dialog (triggered by some bundle command) is not centered vertically: * The size of the completion dialog (triggered by some bundle command) doesn’t always increase to match the content: I’ve included screenshots for each bug, I hope they show up. I’m running TextMate 2.0.21 on macOS Big Sur 11.1. -- /Jacob Carlborg

3 years, 1 month

Hidden files in the file browser?

by Walter Lee Davis

I have hunted through the interface, and I can't find a setting that would allow hidden files to appear in the list in the file browser. I can find those files by using File / Open, which shows me a standard file dialog, and the options in that allow me to see hidden files (that option is checked on, and stays on). But the list never shows them. How is this preference meant to be governed? Thanks in advance, Walter

3 years, 1 month

Data loss bug in 2.0.16

by Paulo Moura

Hi, There's a severe data loss bug in recent releases, including 2.0.16, where trying to undo an edit operation in the editor results instead in an undo of an operation in the file browser pane. If the sound is not muted, you may hear the sound of a file/folder being moved to the trash. But instead the file/folder just vanishes, loosing the work in those files/folders. When this bug occurs, restarting TextMate offers a temporary workaround. Until it happens again. I'm using macOS 11.2 if that's relevant. I'm a registered user of TextMate since version 1.x. Never until the latest releases I have come across this bug. Cheers, Paulo ----------------------------------------------------------------- Paulo Moura Logtalk developer

3 years, 1 month

Failure running “Environment Based on Current Word”.

by andreas.loeffler＠googlemail.com

I am using Textmate for writing LaTex texts and I recently found that I can used a shortcut for completing environments (the help says "by default to cmd and < " but it turned out to be ctrl and <). Still, I get an error message that I did not find in the mailing list: Failure running “Environment Based on Current Word”. Users/andreasloeffler/Library/Application Support/TextMate/Managed/Bundles/LaTeX.tmbundle/Support/lib/Ruby/configuration.rb:29:in `load': Unexpected character { at line 1 (OSX::PropertyListError) from /Users/andreasloeffler/Library/Application Support/TextMate/Managed/Bundles/LaTeX.tmbundle/Support/lib/Ruby/configuration.rb:29:in `load_file' from /Users/andreasloeffler/Library/Application Support/TextMate/Managed/Bundles/LaTeX.tmbundle/Support/lib/Ruby/configuration.rb:28:in `open' from /Users/andreasloeffler/Library/Application Support/TextMate/Managed/Bundles/LaTeX.tmbundle/Support/lib/Ruby/configuration.rb:28:in `load_file' from /Users/andreasloeffler/Library/Application Support/TextMate/Managed/Bundles/LaTeX.tmbundle/Support/lib/Ruby/configuration.rb:38:in `load_user_file' from /Users/andreasloeffler/Library/Application Support/TextMate/Managed/Bundles/LaTeX.tmbundle/Support/lib/Ruby/configuration.rb:20:in `load' from Environment Based on Current Word:6 Unfortunately, I do not understand the source code so I do not know what to do. If I edit the command I see #!/usr/bin/env ruby18 SUPPORT = ENV['TM_BUNDLE_SUPPORT'] require ENV['TM_SUPPORT_PATH'] + '/lib/ui' require ENV['TM_SUPPORT_PATH'] + '/lib/exit_codes' require SUPPORT + '/lib/Ruby/configuration.rb' @plist = Configuration.load shortcuts = @plist['environments'] lshortcuts = @plist['labeled_environments'] if ENV['TM_SCOPE'].match('beamer') then shortcuts.update(@plist['environments_beamer']) lshortcuts.update(@plist['labeled_environments_beamer']) end name = STDIN.read cmd = nil if name == "" then arr = ["custom…",nil] + (shortcuts.keys+lshortcuts.keys).sort ind = TextMate::UI.menu(arr) TextMate.exit_discard if ind.nil? if ind == 0 then name = "" else name = arr[ind] end end options = Array.new for key in shortcuts.keys do if shortcuts[key]['triggers'].index(name) then options << {:cmd => key, :setting => :no_label, :content => shortcuts[key]['content']} end end for key in lshortcuts.keys do if lshortcuts[key]['triggers'].index(name) then options << {:cmd => key, :setting => :label, :content => lshortcuts[key]['content']} end end opt = case options.length when 0 nil when 1 options[0] else ind = TextMate::UI.menu(options.map { |opt| opt[:cmd] }) ind.nil? ? nil : options[ind] end if !opt.nil? then print "\\begin{#{opt[:cmd]}}" print "\n" if opt[:setting] == :no_label print opt[:content] || "\t$0" print "\n\\end{#{opt[:cmd]}}" elsif name == "" print "\\begin{${1:env}}\n\t$0\n\\end{${1:env}}" else print "\\begin{#{name}}\n\t$0\n\\end{#{name}}" end Can anybody point me to something I understand?

3 years, 1 month

Accidentally deleting from the files list sidebar in 2.0.19

by Walter Lee Davis

Twice this afternoon I have inadvertently deleted the current file I am editing. 0. I am using Mac OS 10.15.7 with all available updates. 1. I am in 2.0.19 2. I am editing an existing, previously-saved SCSS file in a Rails project 3. I have used the keyboard shortcut Command Delete to delete all text on the current line, left-wise. 4. There were previously two spaces on the line (not sure if this is important) When I hit this combination of keys, I hear the Trash sound, and the file I am editing disappears from the file list in the sidebar. It does not join its peers in the Git deleted state (there are other files I have previously deleted in the same folder, awaiting their ultimate fate of having that delete committed. Luckily, the file is still open and focused in the editor's buffer when I do that, so simply saving restores the file where it was. If I were listening to a podcast or similar, this could have gotten ugly. I am in 2.0.19 -- I triple-checked. The sidebar file list is in no manner of speaking in "focus" when this happens, my text cursor is blinking at the insertion point where I expect to delete-leftwards. Please let me know if there are any commands I can run while the editor is in this state that might give you further insight into this issue. I'm gonna keep editing for now until I hear from you (fingers crossed) and then I'm gonna restart the whole Mac to be certain. Walter

3 years, 1 month

Title case issue in TextMate

by Angelo Varlotta

Hi, Today while using TM (version 2.0.19 on macOS 10.15.7), I noticed that the title case style doesn't seem to work for words of three letters or less that are not conjunctions or prepositions. I wanted to convert a sentence to title case with the Crtl + Opt + U keys and in the sentence the three letter word 'use' didn't become upper case while the longer words did. It appears that conjunctions and prepositions become title case only for four letter words or longer. Is there a particular style that title case adheres to in TM? The two main style types listed on Wikipedia are the AP style and the Chicago style. Does TM use something different? Title case - Wikipedia <https://en.wikipedia.org/wiki/Title_case> Cheers, Angelo

3 years, 1 month

Bundle window browser inaccessible

by Quinn Comendant

After updating to v2.0.17, when I open the Bundle Editor, it looks like this (screenshot): https://i.imgur.com/4Xhewxw.png The browser section is shrunk down to a few pixels. I'm unable to use the drag handle to resize the panels to reveal the browser section. Any secret tricks to restore the panels to their default size? 😅 Quinn

3 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

TextMate March 2021