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 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?
Hi,
I experience lately on a regular base a high CPU usage of TextMate (TextMate
version 2.0-rc.23, macOS 10.14.3 18D109). I did not install new plugins
(besides of regular updates TM-build in plugins). TM does not crash so I
cannot provide a crash log.
Could it be related to performing a search in a project folder with a large
number of files?
== feek
--
Sent from: http://textmate.1073791.n5.nabble.com/textmate-users-f3.html
Hello,
I've recently updated to Mojave and I noticed that a TextMate theme I
use called iPlastic doesn't allow a transparency for the background. For
the same background setting in High Sierra the background now is solid.
I've tried modifying the theme directly in the Bundle editor and tried
different color codes for the background entry, which was
background = '#EEEEEEEB';
before the OS update, but I haven't been able to add any transparency.
Does anyone have suggestions?
Angelo
Hello,
I've noticed that sometimes files that are not empty sometimes appear so
when I open them in TextMate. If I close and reopen them, they still appear
blank. If I open them in TextEdit, they don't appear empty. The problem
goes away, though, when I quit TextMate and reopen it.
This is a little inconvenient, because I sometimes have several files open
and then have to close and reopen all of them, too.
Would anyone know how to have the file open properly without having to quit
TextMate?
Thank you and best wishes,
Anthony V. Pulido
Hello,
I'm running TextMate version 2.0-rc.27.
It seems that I'm no longer able to edit files that are not owned by
me by using `sudo mate` or plain `mate`.
Steps:
1. Run `sudo mate /etc/hosts`
2. Enter my username and password in the terminal
3. Make a change
4. Save the file
Expected: The file is saved with the new contents
Actual: an error modal is show with the following contents:
Title: The document “hosts” could not be saved.
Body: Failed replacing hosts with
/var/folders/w8/0pc0dw1d4zd9knf_qm4ls1bc0000gn/T/TemporaryItems/(A
Document Being Saved By TextMate)/hosts: You don’t have permission to
save the file “hosts” in the folder “etc”.
So far I have tried:
- Granting "Full Disk Access" to TextMate in System Preferences ->
Security & Privacy -> Privacy
- Uninstalling and reinstalling `mate`
Please let me know if there's any more information I can provide.
Thanks!
Hello list,
when opening (existing) files from Terminal.app using the `mate` command, it occasionally (but not always) takes a fairly long time (more than 5secs) to open the file in TextMate. TM in all these instances is already running, but doesn't necessarily have any open windows.
This is for small files (e.g. 30 short lines of code), so it cannot be the file size making a difference. If I open the files directly through TM's File -> Open... menu, no such delay happens.
During such a delay, if I click on the already running TM in the dock to activate it, the desired document that `mate` is trying to open immediately appears.
If I close the document and retry immediately afterwards, then no delay seems to exist for a while. Swap also doesn't seem to be an issue, my swapfile has size 0 on a 32GB Macbook Pro, with 16GB free. If TM hasn't been activated in a while (even though supposedly running according to the Dock dot) then this seems more likely.
It seems to be the communication / connecting between mate and TM that causes this delay somehow. I've tried removing and reinstalling the `mate` command.
This is on TextMate version 2.0-rc.10, but is not new behavior, I've seen this for quite some time.
Does that sound familiar to anyone or have any diagnosis tips?
Thanks,
Daniel.
