[vim-tmux-navigator][1]:
> Seamless navigation between tmux panes and vim splits
Add the hybrid vim/tmux plugin `vim-tmux-navigator` to switch between
tmux panes and vim splits with `C-[hjkl]`.
Add vim-tmux-navigator as a submodule in tmux/plugins and create a
symlink from vim/pack/plugins/start.
Get rid of similar switching keymappings in the vim and tmux configs.
[1]: https://github.com/christoomey/vim-tmux-navigator
> Sorting folds is not easily possible in vanilla vim. You could join
> all lines in a fold, sort and split them up again; however, it is time
> consuming and tedious.
>
> This little plugin solves that issue: It sorts a visually selected
> region while keeping closed folds intact. Since folds can be created
> in a variety of ways, it is therefore straight-forward to sort
> arbitrary groups of text based on their first line.
> This Vim plugin provides text objects for comments.
>
> `ac` selects a comment including the comment delimiters and `ic`
> selects just the comment content. (There's also a third text object,
> `aC`, which selects a comment including trailing or leading
> whitespace.) These mappings are available in Visual and
> Operator-pending mode.
>
> This plugin uses the `comments` and `commentstring` settings to
> determine what a comment looks like for a given filetype. It works
> with both `/* paired */` and `// simple` comment delimiters.
>
> This plugin depends on the textobj-user plugin.
And load vimtex automatically. I discarded the autocommand as vimtex
only loads a small ftdetect script for tex and the rest of the plugin is
made up of ftplugins, indent files, etc. by itself.
The overhead of the autocmd feels bigger than just loading the small
component and letting vim doing the rest.
(But this is in now way tested/benchmarked. That is just how I feel and
it makes it a tad cleaner)
And move the plugin specific keybindings into 40-keybindings.vim.
`packloadall` sources the plugins directly in contrast to `packadd`.
Because of that we can access the `g:loaded_*` variables and do not have
to specify our own keybindings for vim-surround as now the user bindings
are loaded later and overwrite possible clashes.
