41–50 of 176 posts
Vim, apparently, is the new emacs. /me ducks and runs out of the room
You forgot to press ESC before typing that, so...
CTRL-D
sudo apt-get remove vim
sudo apt-get purge vim
See, it’s not hard at all to learn the proper way to use vim!
I couldn't agree with this more. Also undotree [1] should be built into Vim as well. Vim represents undo/redo under the hood as a tree, which is absolutely incredible once you have a plugin that unlocks it, but the built-in facilities for traversing that tree could be charitably described as "dismal".
Vim's undo tree makes a solved problem out of the old "undo undo undo undo undo... ok what did this file used to look like... redo redo y... oops did I just press 'y' by accident instead of redo and blow away a bunch of my later edits... next time I should remember to commit before I do that (even though I totally won't)" situation, but without the plugin, it's effectively inaccessible.
[1] https://github.com/mbbill/undotreeInteresting read, I've been using Vim for some 18 years myself and I was completely unaware of fzf. However, I'm curious if you know `rg` (aka. ripgrep): https://github.com/BurntSushi/ripgrep In my experience it's markedly faster than `ag` (which is markedly faster than `grep`).
Interesting read, I've been using Vim for some 18 years myself and I was completely unaware of fzf. However, I'm curious if you know `rg` (aka. ripgrep): https://github.com/BurntSushi/ripgrep In my experience it's markedly faster than `ag` (which is markedly faster than `grep`).
"The vim-surround plugin is so useful that it should probably be built into Vim." I couldn't agree with this more. Also undotree [1] should be built into Vim as well. Vim represents undo/redo under the hood as a tree, which is absolutely incredible once you have a plugin that unlocks it, but the built-in facilities for traversing that tree could be charitably described as "dismal". Vim's undo tree makes a solved prob…
With Tab mapped to :WSNext (and C-Tab to :WSPrev) I can see all open buffers and cycle through them. And close unnecessary with :WSClose.
I'm an avid tmux+neovim user, too, though working with Reason is a lot easier in VS Code. Making the switch from actual vim to fake vim (ie JS emulation) sucks. Recently, VSCodeVim merged #1725 to add actual neovim as an editor - it's using NeoVim's embedding API so you're using neovim to edit the text file inside of VSCode's chrome, including all of VSCode's type hints and popups. Info here: https://github.com/VSCod…
Personally I’d prefer that to working in GUI with an embedded terminal.
I would not remap , and ; as the article suggests, since those keys are already used in Vim for repeating f/F/t/T.