41–50 of 63 posts
":, @: ": is the register storing the last executed command. You can write ":p to print it to the buffer. @: reruns the last command. That seems like a mouthful. I use : to run the last command and some more to run the ones before that.
And if you wanted to repeat that 10 times you would...?
I guess I might press and hold at ten.
I’ve discovered q: when trying to quit vim in a hurry. You always keep finding new quirky things to do in vim but I guess the same hold true for other text editors like Emacs
That's how I found `K`. I was surprised the first time I got a man page open. Now I find it pretty useful and wish it extended to more than man pages.
au FileType mail set keywordprg=~/bin/dictlessThe problem is, how do you remember all of this stuff? Tabdo/bufdo is as advanced as it ever gets for me.
https://www.invidio.us/watch?v=wlR5gYd6um0
Unfortunately, this aspect is poorly documented. Thoughtbot's video is among the best I've found. And that's with 30 years' experience.
":, @: ": is the register storing the last executed command. You can write ":p to print it to the buffer. @: reruns the last command. That seems like a mouthful. I use : to run the last command and some more to run the ones before that.
And if you wanted to repeat that 10 times you would...?
Earlier quoted context omitted.
At my billing rate "15 days straight" is approximately equal to a low end BMW. So I think tabdo/bufdo will have to do for now. At least until I get a salaried job and can learn the rest at my employer's expense. I do think there's Pareto principle at play with all this obscure stuff. Knowing 20% gets you 80% of the benefit, every additional percent gets you exponentially smaller fraction of the remaining 20%. That's…
>At my billing rate "15 days straight" is approximately equal to a low end BMW. So, you’re saying you are making too much money to learn something new?
"Exobrains, on the other hand, stuff Vim full of plugins, functions, and homebrew mappings in a vain attempt to pretend they’re using Emacs." This is disturbingly accurate from my point of view. I keep wondering if I should finally jump ship and stop tweaking vim with questionable results. Spacemacs? Pure emacs + evil? Suggestions welcome.
Spacemacs is peanut butter meets chocolate. Apps like Magit and org-mode with vi's modal editing are truly superior.
The discover ability of Spacemacs is really second to none and makes it much faster to learn and keep learning.
Spacemacs is Nutella to keep the analogy going...
"Exobrains, on the other hand, stuff Vim full of plugins, functions, and homebrew mappings in a vain attempt to pretend they’re using Emacs." This is disturbingly accurate from my point of view. I keep wondering if I should finally jump ship and stop tweaking vim with questionable results. Spacemacs? Pure emacs + evil? Suggestions welcome.
I use gf (mnemonic: go file) all the time -- it will grab the string under the cursor (the cursor doesn't need to be at the start of it), then attempt to open a file with that name. You can look up the details but it uses a path type mechanism so if the name of the file isn't absolute, it will check the path.
While I do have a few of these IDE-like plugins (undotree, for example), I think it's better to try plugins which embrace the "vim way" first before investing in a full IDE-like plugin. I don't mean to gatekeep by criticizing IDE-like plugins, but just to say that spending the time to learn normal mode as a true language (verbs, nouns, and all) and using plugins that follow this idea is a worthy investment. Then, add IDE-like plugins to work around the frustrating rough edges of vim once you've milked all that you can out of it.