dotvim VS vim-commentary

I have a whole file full of mappings like this that let Vim recognize various special key combinations from any terminal emulator I've used in the last 20 years. It's a mess: https://github.com/mgedmin/dotvim/blob/master/plugin/keyboard-workarounds.vim

https://github.com/mgedmin/dotvim, accumulated over many years.

So, three out of four? https://github.com/mgedmin/dotvim

Assuming I understood your desire correctly? I have a function to jump to the original (or patched) file when I press Enter on a line of diff: https://github.com/mgedmin/dotvim/blob/master/ftplugin/diff.vim

I use a custom foldexpr. I've been using it for many years, and polished it to do the right thing on all the codebases I've used it on.

My ~/.vim/ is a Git repository and I make it support older versions of Vim by checking for the existence of features before using them, because I couldn't stand my .vimrc emitting any errors on Vim startup. If you're interested, it's here: https://github.com/mgedmin/dotvim/

The primary reason why I need timeout/ttimeout is to have a working Escape key, when you also want to have custom bindings for various key combinations (e.g. ctrl+shift+arrows) that aren't natively recognized for your terminal for some reason, and thus you end up creating compatibility mappings for them.

My ~/.vim is here, if you're curious about the details: https://github.com/mgedmin/dotvim/

I'm perfectly happy with ~/.vim in a separate git repository (mine), with all the plugins installed via vim-plug.

My vimrc is, uhh, big, but I've tried to keep it commented.

Also, tpope/vim-commentary

https://github.com/tpope/vim-commentary does what you expect!

I've replaced most of my custom maps for commenting with tpope's commentary plugin. It's a great plugin. However, I wasn't happy with the lack of multi-line/block comment abilities so I created some maps to compliment the commentary plugin. Here are some maps that can be used with autocmd, FileType and for JavaScript comments.

commentary.vim + :h gq?

Having said this, there are some useful language independent extensions: jiangmiao/auto-pairs, tpope/vim-commentary, preservim/tagbar, junegunn/vim-peekaboo

vim-commentary comment code comfortably with motions and visual selections alike.

With a plugin like vim-commentary or comment.nvim

" This file contains common and basic plugins too essential not to include " See https://github.com/junegunn/vim-plug/wiki/tutorial " Auto install vim-plug (if not already installed) if empty(glob('~/.config/nvim/autoload/plug.vim')) silent !curl -fLo ~/.config/nvim/autoload/plug.vim --create-dirs \ https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim autocmd VimEnter * PlugInstall endif " Run PlugInstall if there are missing plugins autocmd VimEnter * if len(filter(values(g:plugs), '!isdirectory(v:val.dir)')) \| PlugInstall --sync | source $MYVIMRC \| endif " enable Vim-Plug: call plug#begin('~/.config/nvim/plugged') " Install/update plugins Plug 'https://github.com/tpope/vim-commentary.git' Plug 'https://github.com/morhetz/gruvbox' " Better C/C++ syntax highlighting; Plug 'https://github.com/jackguo380/vim-lsp-cxx-highlight' call plug#end() "---------- Basic configs ---------------------------------------------------- autocmd vimenter * ++nested colorscheme gruvbox " Enable transparent background let g:gruvbox_transparent_bg = 1

Commentary Tim pope's comment plugin