lh-vim-lib VS lh-misc

and it seems it depends now on lh-vim-lib (to be able to set dictionaries: :let b:dict.key.subkey.whatever = 42: https://github.com/LucHermitte/lh-vim-lib (install it with your plugin manager)

Note that if it's just for setting a few standard options, editorconfig will be enough for most of us. It won't work if you want to define different mappings, or if you want to change the path to your snippets (actually editorconfig plugin could be hijacked to set vim variables)

here an UI alternative to confirm() and another that implement comboboxes: https://github.com/LucHermitte/lh-vim-lib/blob/master/autoload/lh/ui.vim (the code is very old, but it works search for getchar())

Regarding project management, .exrc is enough as long we're working on simple project where everything is in the same directory. On real project I've ended up needing and writing much, much more.

or in your .editorconfig file (if you have any) as lh-vim-lib also registers an extension to set vim variables from editorconfig file -- it's definitively not meant to be used this way, but well it's possible.

I have things on the same topic in my vimscript library: I provide a queue object into which I register related tasks that cannot be safely parallelized.

the plugin file to drop in ~/.vim/plugin/: https://github.com/LucHermitte/lh-misc/blob/master/plugin/let-modeline.vim

Note: as I often install clang on machines where I'm not root, I often have to feed these paths to the LSP server I use, or even to libclang. In the end, I automatically ask the pathnames after Vim has started (system() cannot be used directly in the vimrc), and feed them to ccls (through coc).

First if your installation of clang+libc++ is non standard (/usr/(local/)), you'll have to register the path to the system includes (which can be automated).