Thanks to @jobojeha for the suggestion

Automatically adds GC roots, including a fix for an implicit interactiveBash dependency

Doesn't work well when languages are mixed

Binding Ctrl+Tab is problematic in most terminal emulators.

Dependency of vim-fzf's git integration.

LSP based navigation in a header-centric codebase turned out to be not
that much better than plain ctags. The latter has the advantage of being
both the most performant and most simple to setup.

The main problem with e.g. cquery is that its underlying JSON compilation
database only maintains information on compilation units i.e. cpp files.
In this situation navigation in header files frequently reverts back to
plain guessing which provides no advantage over ctags.

Added vim-gutentags for automatic regeneration on file save.

Feels less distracting and faster. I don't actually want to turn this
vim setup into a always active intellisense-like experience but rather
have code introspection quickly available if I actually need it.

Seldomly used, performance doesn't matter as much.
Other narrowing searches are still performed by fzf.

* Use integrated plugin manager
* Switch to nvim instead of continuing to maintain a config for both vims

Config is shared with custom-vim

To be generated using [tree.kummerlaender.eu](https://github.com/KnairdA/tree.kummerlaender.eu).