TextMate February 2021

textmate@lists.macromates.com

27 participants
13 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

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

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

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

Quicklook not working for latex files

by Anthony V. Pulido

Hi everyone, There was once a time when I would press the spacebar on a tex file in the Finder and I would see a Quicklook preview of it using the theme I used when TextMate is open, complete with syntax highlighting, etc. I'm not sure what I did, but now when I press the space bar, I see only a picture of the document icon with the TextMate logo on it. It does correctly label it "TeX" with that capitalization, though. To experiment a little, I deleted the line <string>tex</string> in the TextMate.app Info.plist. Quicklook now works on tex files, but it looks like it's using the built in macOS ql plugin for plain text. That is, it's not using the default TM theme and thus there isn't any syntax highlighting, etc. When I put back <string>tex</string> in Info.plist and then do touch TextMate.app, it goes back to the preview of the document icon as before. I don't mind the Quicklook preview without the theme colors, but it would be nice to restore TextMate's Quicklook, if possible. I'm using TM 2.0.17 on macOS 10.15.7. Best wishes, Anthony

3 years, 2 months

Scroll position jumping on changing tab?

by Andrew Hodgkinson

It's been great to see the incremental improvements in TextMate over time. The recent 2.0.17 has a really nice fit and finish all-in and it's still by far my preferred "fully native" text editor - a first choice for development. Little things like the recently shuffled themes menu to support dark/light mode switching are always very welcome and have a surprisingly big "quality of life" impact. Of course I've a niggle ;-) - I noticed in 2.0.6 (possibly earlier?) that when switching between tabs (currently macOS 11.2.1, but it's done it for a while) TextMate will sometimes shift the view scroll position after a fractional delay. It seems to be related to any lines that aren't of a fixed height; for example, comments in Ruby source code have always word-wrapped even if word wrap is disabled and if there are any of those in a piece of text above the caret position then there's a good chance of scroll position jumps when switching between tabs. The issue is especially pronounced in larger Markdown docs when I usually edit with word wrap enabled - in that case, the jump can be severe and disorientating as the view can end up somewhere very different from "where you left it", but the caret position is unchanged and might not even be on-screen anymore. As an example, a large README.md file for our application was scrolled with line 656 at the view midpoint with caret placed there, so that line 633 was at the top of the view. I switched to another tab then back again and after a brief delay the view jumped so that line 602 was at the top of the view and line 656 wasn't even visible. This jump doesn't happen with word wrap turned off, but *does* still happen if I've allowed the Textmate configuration to change font sizes on headings. It just "feels like" there's some kind of scroll position recalculation happening on a thread whenever a tab regains focus, but this calculation isn't accounting for "unusual line heights" due to line wrap or (maybe) font sizes. Just me? -- TTFN, Andrew Hodgkinson Find photos, software, music and more at my home site, Bandcamp and GitHub: https://pond.org.uk / https://pondnz.bandcamp.com / https://github.com/pond

3 years, 2 months

Handling multiple caret selection in bundle command

by Chris Ross-Gill

Hi, I'm doing a little housekeeping on my Rebol bundle. I've one command that takes a selection, evaluates the content and replaces the selection with the product. I'm using TM_SELECTION to determine the various selection modes: • No selection: use TM_CURRENT_LINE as input • Regular selection: use TM_SELECTED_TEXT as input • Columnar selection: use TM_SELECTED_TEXT splitting on LF I don't currently handle multiple caret selection, though I see that I can read from STDIN to obtain that input. The tricky part seems to be discerning how to break that input to match the respective selections. I could split by LF, though that doesn't work if any of the selections themselves span multiple lines. Otherwise it seems it's a walk through each line to match up with the TM_SELECTION entries (which I've not attempted thus far, in fairness). Am I missing anything obvious here? Has there been any consideration of using some of the ASCII field separators (e.g. 0x1D-1F) to delimit these and permitting use of said separators as a way of directing the response to fill each of these selections respectively? Thanks, – Chris

3 years, 2 months

Re: Bundle window browser inaccessible

by Phil Molyneux

I have the same problem as Curt Selmer with the Bundle Ediror — I am running macOS 10.14.6 Phil ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Phil Molyneux E: molyneux(a)pobox.com T: 020 8549 0045 M: 07885 426 323 71 Deacon Road, Kingston upon Thames KT2 6LS ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3 years, 2 months

Save files with newlines preference?

by Walter Lee Davis

Is there some way to enforce a trailing newline on new file create (and update)? Is this a plugin-shaped problem, or a preference I can set? Thanks, Walter

3 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

TextMate February 2021