4 ms·
Partially offtopic. The author is doing > "complex edits [in Emacs] using Vim macros" This is a big surprise. I left vi for emacs in the early '90s when vi's
by pmontra 11y ago
Partially offtopic. The author is doing
> "complex edits [in Emacs] using Vim macros"
This is a big surprise. I left vi for emacs in the early '90s when vi's macros were crippled, to say the least. I'm using vim for quick edits, mainly on servers or configuration files (sudo vi /etc/something). Did vim macros really become better than Emacs' ones?
- DigitalJack 11y agoVim's macros are super easy to record and play back, repeatedly. It's the one thing I'll still use evil mode for. Emacs isn't that much worse, vim is just faster and easier.
- scottaj2 11y agoExactly this. I have the muscle memory built so I can just bang out the macro really fast, and evil lets it contain a mix of vim or emacs commands.
- chowes 11y agonot sure about "better", but i'm curious what was crippling back then? using them nowadays is a breeze and you get practically full functionality at your disposal.
- pmontra 11y agoYou could have one macro per time and you had to type it in like this :maappend chars to end of line( * )Jf:D Then ^N to execute it, I think. ( * ) I don't remember how we quoted ESC When I saw that emacs could record macros while I was typing that immediately sold me the editor. Multibuffer and multifile were nice features too.
- catern 11y agoThe author is actually just using Emacs macros with vim-style keybindings. Emacs macros are still probably more powerful.
- emidln 11y agoVim's macros are certainly more quickly composable. I still use them in emacs via evil using execute-kbd-macro: ;; select the current graph (execute-kbd-macro (kbd "ma{y}`a"))
- sspiff 11y agoSame here, I use vim for editing a single file (often scripts or configs), always in a terminal. For editing multiple files (mostly code) or a project folder, I use emacs with X11.