TextMate 2.0 (rc 10)
github.com
github.com
Obviously for many people this really doesn't matter but a niche of people this is a huge advantage.
I'd love to experiment with various editing models but hate the idea of implementing the entire GUI layer. Also I'm dying for a pretty GUI for Kakoune (my editor of choice).
I'd pay hundreds for this honestly. Maybe I'm too niche for it to matter, but I feel like these companies putting so much work into their editors are not fully utilizing the effort they put into it.
Ie, many don't want to switch from Vim, but if we could take a really well polished and established editor like TextMate and make it the GUI for Vim? Well that's just amazing. I'd buy it hands down, for quite a lot. It would need to be full access though, and not explicitly tied to (Neo)Vim.
Maybe Textadept also offers what you want? https://foicica.com/textadept/
It seems a very tough (if not impossible?) problem describing the GUI/editor relationship in a generic and thin API, because of each one's many designs interacting with their usual interface. I would like to follow a project attempting it though!
What do you mean by “being full access”?
(separating the engine from the GUI)
In general I just meant that the GUI would attempt to reduce assumptions and be as flexible as possible. Ie, I would want to be able to control multiple cursors. Control multiple highlights. etc
Bonus points if it provided various events to trigger built in IDE features like auto complete popups, debug breakpoints, file panes, etc.
Fwiw, I don't think a "generic" interface is ideal. Perhaps for basic editor tasks, but when writing a kak<->sublime (fake example), I think it's acceptable to write it specifically for sublime. Having that binding be interchangeable between sublime, atom, xi, etc seems overreaching with little to gain.
Though, to a degree a subset of general commands which all editors support would be really handy. Similar to the Language Server Protocol, if Sublime implemented the fake "Editor Server Protocol" it would allow Sublime to instantly support Kak, Vim, Nano, etc. ESP extensions for Sublime, VisualStudio/etc would provide full functionality without affecting the ESP Core.
Hmm, this is neat. Perhaps a bit lofty, I just want a nice GUI for Kakoune hah.
It looks horrible out of the box, but it looks as good, if not better than most modern editors.
It runs on the jvm and so is sluggish to launch, but it's an extremely mature product and the plugin ecosystem is nice. Getting the latest plugins is a bit hit or miss, but it's worked great for me and my colleagues.
Font rendering is awesome and has support for ligatures etc.
For what it’s worth if anyone is considering switching here are some pros and cons that I personally found. It’s largely based on my specific tastes as well so please if in doubt do try as they’re both excellent software.
Some pros of Textmate(IIRC it was 2.0rc1 or there about):
- the SSH support was very good. Textmate has functionality for this called rmate that lets you edit remote documents and I found it to be very fast and IMHO preferred this over tmux + vim for pure editing of remote files
- textmate has a decent ecosystem of plugins I felt. Lots of themes and bundles for all kinds of features and languages.
- out of the box editing experience is relatively well featured in broad scope
The down sides:
- while I felt like textmate had lots of good third party bundles a lot of them also were really old and were not well maintained. Even some that are maintained dont see tons of updates
- at least for the languages I used (mostly a web stack of JS SCSS/CSS HTML and Python) the autocomplete would leave much to be desired if there was any at all. In parcular I could never quite get Jedi to work with it for python (and the listed bundle in their readme doesn’t really work and updating it wasn’t going well for me) and forget about typescript definition files. I don’t know if this changed at all.
- the API (to me) was a little terse and I didn’t feel it was super well documented IMO. I also found that a lot of the documentation wasn’t or didn’t feel like it was as current as the API could handle too and examples that were up to date are very sparse.
So generally if you rely on very good autocomplete like you get in VS Code, Atom, or an IDE it might not be the best fit for you. This of course was at the time and a lot of this may have improved I have not investigated this in some time.
I have similar feelings about BBEdit for what it’s worth.
Look under Edit > Column Selection Mode. I think it's bound to Cmd+Shift+8 by default.
If you have a set of lines selected, it will transform them into multiple individual selections too.
PS Textmate 3 should be subscription based to support the next generation of Mac text editor!
As for me, I've been using TextMate since it's first release more than a decade ago, and I'm simply used to it. I'm more productive in TextMate since I know where everything is without thinking about it.
Compared to Sublime: Better Find interface. I really hate the sublime multi-file search result list, it seems like a hack, not a real interface... I just don't get why they would do it like that.
I just timed it. Opening a new window on the PC I'm using right now takes between 70 and 72 frames, or between 1.16 and 1.25 seconds. On the rare occasion that I do it.
I understand that everyone is a leet uberhacker who is thrown off their flow by a butterfly farting on the breeze, but this is princess-and-the-pea stuff.
1. Fast and responsive 2. If you write a plugin, you know TextMate is Unix (forked child process, communicate through shared fd, you invoke a command named dialog2 to let TextMate popup any dialogs or completion menu...). You can add editor commands in any language -- you can even make TextMate display complex UI dialog with bash. 3. File browser is nearly a finder (drag and drop like finder, and most finder shortcuts work) 4. Search (there are some hidden shortcuts, but when you master it you feel very fluent)
There are weakness too: TextMate is losing the market, many bundle developers switched to other editors. You can't find many new bundles nowadays. It still doesn't support vim-like keyboard operation... etc
The rise of this phenomenon is doing more than almost any other event to drive me to FOSS options.
Of course the subscription model gives JetBrains more incentive to keep revving the version number so if you want to stay up to date with the latest and great you have to keep "buying" it every year but C'est la vie.
More info for those interested https://sales.jetbrains.com/hc/en-gb/articles/207240845-What...
* n++ has good replacing when using new lines like \n. And regex.
* n++ column select is very good
* n++ makes it easier to create a new tab
* In n++ when I double click a word, all instances of that are highlighted. Not so in TextMate
"find_selected_text": trueTextMate comes closest on the Mac which is why it's my primary GUI editor, but I still miss being able to do all the stuff that just came "naturally" in Notepad++.
Also, running Notepad++ in Wine just doesn't feel the same.
For TextMate, cmd+E, cmd+F then the selection is in the search box. Or, you don't even have to open the search box with cmd+F, just cmd+G to next selection or cmd+opt+F to multi-cursor edit all occurrences.
The regex in TextMate is also very powerful (the unicode support is more powerful). New lines can be matched with \n. Another way is to select new line and repeat the cmd+E trick.
TextMate column selection is even better: you can enter column select mode simply by pressing opt. It is in fact multi-cursor editing, many editing commands like completion / copy / paste can work for each row individually.
Cmd+N or ctrl+cmd+N in TextMate.
The last one, not in TextMate. Though cmd+E then cmd+opt+F can highlight and start multi-edit on all instances of the word.
* TextMate has amazing regex support. I replace multi-line stuff all the time. Best i've found.
* TM column select is most likely just as good, and it has multi-select (non-column based multi-selection). (I don't know the in's and outs of n++ to comment)
* TM uses the usual command-t for something else, but command-option-n isn't too bad for a new tab.
* command-e to prime selection, then option-command-f to selects all. These are real multi-selections not just highlights, so you can edit-all, copy-paste, etc.
Not sure how it works exactly with Textmate, but for most Mac editors, you double click a word, cmd-E to place the word in the search box, then cmd-G to find again. This saves time because you never see the find dialog and can start searching immediately. I only use cmd-F if I need to fiddle with the find settings. Replacing is just as simple, shift-cmd-E to place selected word in the replace field, cmd-T to replace and find again.
I've been using Sublime Text for a long time, and briefly used Visual Studio Code, and all the actions you've mentioned are supported (if I've understood them well).
However, I'm curious if I'm missing something.
Other editors get the other side of the coin wrong, and don't have all the movement operators needed to do a some jobs (word-move while selecting/deleting to remove ragged whitespace).
That all said, there is a big component of what one is familiar with. I'll admit TM's multi-select was the first good implementation i've used and haven't strayed too much since.
The only thing lacking for me is split windows but it's not that hard to undock one tab and push it to the left and the other one to the right.
What do you get when purchasing a license? http://shop.macromates.com/
(I'd love to read the story of TextMate)
I actually cant find these last modified dates you refer to. The footer just display this for me:
MacroMates Ltd. — Cyprus — HE 259033 — VAT CY-10259033PThat, and the blog that was last updated four years ago.
I do remember paying for TextMate. Once.
The Perl bundles come in handy.
I know it's strange, but as someone who began a career on teletypes with greenbar paper, I sometimes like to see code on a printed page that I can scribble upon.
Would be nice to know what's new in v2.
Looks like 2.0 has been a WIP since 2013 though? Not sure.