21–30 of 123 posts
So even if you have neovim set up as your "vi", you'll probably still have an "ex" available on your command line. It'll just be symlinked to legacy vim, not neovim.
Earlier quoted context omitted.
aka "Oh, that's the key I have been hitting by accident"
Yea, I finally got fed up one day and put nnoremap Q in my .vimrc. No more "how did I get HERE?"
This way, I can skip the awkward @q step, and keep hitting Q instead of @@ to re-run the macro.
While I don't particularly care for ex-mode, I think it's weird to be calling it Neo 'vim' without it. If it's going to become more of a radical departure from Vim and start omitting features as well as adding, I would rather they change the name of the project instead, one that alludes to its Vim heritage rather than having a prefix that means 'new'. Is it a new version of Vim? Or an editor that started as a fork of…
Throw the baby out with the bath water much?
(I've gone and elaborated on my own comment. I might have misworded my intent.)
AFAICT, ex-mode is usually used for scripting, as an alternative to sed, awk, and/or perl. So even if you have neovim set up as your "vi", you'll probably still have an "ex" available on your command line. It'll just be symlinked to legacy vim, not neovim.
For those who, like me, had never heard of Ex-mode: https://en.wikibooks.org/wiki/Learning_the_vi_Editor/Vim/Mod...
So they have a mode you enter when pressing q (which quits many other programs) that you can't leave if you don't know the leave command?
This is comedy gold. :D
Earlier quoted context omitted.
Yea, I finally got fed up one day and put nnoremap Q in my .vimrc. No more "how did I get HERE?"
I usually record my throwaway macros to q (because hitting qq is so easy), so I've bound Q to 'call the most recently defined macro'. I would post something to put in your .vimrc, but I use the vim emulator evil-mode in Emacs. This way, I can skip the awkward @q step, and keep hitting Q instead of @@ to re-run the macro.