I've been using TextMate for years and I'm productive and happy with it. However, I like to try other editors from time to time to see if I'm missing anything. Recently I spent some time learning Vim and I discovered a few things that I particularly liked.
1) Split windows -- not the kind of split windows you normally get in Mac applications, but the Vim style ones. In Vim you can easily navigate from the keyboard to your different splits and choose what files to display in each. Additionally, you don't have to reach for your mouse to create a split. When you split, Vim divides the space up for you which is what you want most of the time. I found that it is very handy when needing to view more than 1 file at a time, which in my case is most of the time. Closing splits is about as easy as they are to create -- all from the keyboard. Multiple windows isn't really the same thing because they are slow to setup and tear down.
2) Selective multifile grep -- in Vim you can use a regular expression to open a set of files, and then just grep across the open files.
3) Don't need arrow keys -- after years of editing with the mouse; I find it painful to reach for it. It hurts my right shoulder and shoulder blade. It even hurts to have to move my hand down to the arrow keys. However, in Vim it is easy to keep your hands resting on your keyboard with your shoulders relaxed. No reaching for the mouse or arrow keys.
TextMate 1 or 2, is there a way to auto-highlight all occurrences of
selected word?
I was from Windows using EditPlus, when I double-click or Ctrl+W to select
a word, EditPlus is able to automatically highlight all occurrences in a
different background colour, very nice and useful feature.
With TextMate I have to additionally hit Opt+Cmd+F, and highlighting colour
is same as selected word, not eye-catching. I use 'soft' and light
background for selection background but I prefer bright background (eg
yellow) for highlighted words.
Ctr-S not really meets what I need.
Thanks.
--
Sent from my mobile. Ignore the typos unless they're funny.
I created an issue for this in github.com/textmate/bugs (https://github.com/textmate/bugs/issues/33), but perhaps that issue tracker isn’t monitored any longer.
After upgrading to MacOS 10.15 (Catalina), scrolling through a large file (>6000 lines) often does not properly paint the text. This can be temporarily corrected by dragging a selection over the missing text.
• OS version: MacOS 10.15 (Catalina)
• Textmate version: 2019-09-15 (v2.0)
• Affected file: https://github.com/w3c/json-ld-api/blob/master/index.html.
• File language: HTML
Most recently, I noticed this when moving to line 3500 in the referenced file and scrolling downwards.
Gregg Kellogg
gregg(a)greggkellogg.net
Nice to see Touch Bar improvements: Thank you!
Be nice if the "open recent project" touch bar button _closed_ this window if touched while window is already open.
Can touch bar icons respond to which window is frontmost?
If so, it would be helpful when the Find window is frontmost, to have
1. A touch icon for the "regex" check box (what is the short cut for that?)
2. Tie the “<" and “>" touch icons to window "previous" and "next" buttons.
Having a touch icon to select surrounding braces {} for selecting surrounding braces would be useful.
Having touch icons for "the Ts" would be helpful:
1. a touch bar icon ("fun”?) for cmd-cntr-T ("Select bundle item")
2. a touch bar icon "TODO" for cntrl-shift-T (TODO list)
3. a touch bar icon "symbol" for cmd-shift-T (symbol jump)
Best, tim
> On 18 Aug 2019, at 16:49, Ronald Wampler <rdwampler(a)gmail.com> wrote:
>
> On Sat, Aug 17, 2019 at 6:14 PM Curt Sellmer <sellmerfud(a)gmail.com> wrote:
>>
>> I have been playing with the touchbar support in texmate and have noticed the following.
>>
>> If I set bookmarks in my document the touchbar buttons with up/down chevrons will correctly take me to the previous or next bookmark respectively.
>>
>> However, if I make a change to the document and save it. I now get a change marker showing that it is different than what is in the git repository. That is to be expected.
>>
>> But now the up/down buttons on the touchbar stop at all of the git markers as well as the bookmarks. Is this by design?
>
> Yeah, I wanted to make it easier to navigate other marks (not necessary
> the git markers) without adding yet another up/down arrows button in the Touch
> Bar. But, I agree it probably should have been just to navigate the bookmarks.
> I'll submit a PR to change the behavior.
>
>> It makes jumping back and forth between a couple of bookmarks painful if there are a lot of edits in the file.
>>
>> I can still hold down the fn button and use F2/Shift F2 to achieve this, but that sort of defeats the purpose of having the nifty touch bar buttons.
>>
>>
>>
>> _______________________________________________
>> TextMate mailing list
>> TextMate(a)lists.macromates.com
>> https://lists.macromates.com/listinfo/textmate
>
> _______________________________________________
> TextMate mailing list
> TextMate(a)lists.macromates.com
> https://lists.macromates.com/listinfo/textmate
I do a lot of find using the "In Folder" setting.
A hassle is that actions often move the Find window to be not frontmost.
The only easy way to bring it to the from is cmd-F, but this re-sets the "In: <where>" dropping down to the default, which is document.
If possible, I'd love this behavior to change to leave things as they were. Preferably even between open/close of the Find window, but certainly when the only actin of cmd-F is to bring the window frontmost, not toggling to a default state would be GREAT.
thoughts?
Opened a file from an email attachment
On save from textmate, I get this error:
The document “BadFactorScoresExample.R” could not be saved.
Failed replacing BadFactorScoresExample.R with /var/folders/66/wrbbw2d11gzds_76wqw367f00000gn/T/TemporaryItems/(A Document Being Saved By TextMate)/BadFactorScoresExample.R: You don’t have permission to save the file “BadFactorScoresExample.R” in the folder “7DBA5AD0-07BF-4399-B649-CDE020317A4B”.
FYI, it also generates errors from commands that need to read/write
Since updating to Catalina, I notice that some of the bundle menus are double-spaced. Not all of them, but some. It also seems like any option that has sub-options does not behave this way.
Walter
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:
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?
