vim-addon-local-vimrc VS confiture.nvim

You can? I'd never heard of this. Until now, I'd always used MarcWeber/vim-addon-local-vimrc. It works okay but if there's something built-in I'd much prefer that.

https://github.com/MarcWeber/vim-addon-local-vimrc does the job just fine.

Project-specific editor config: vim-localvimrc, vim-addon-local-vimrc

vim-addon-local-vimrc (project-local settings in a secure way, never use project-local settings without)

VERY IMPORTANT: Do not set your Neovim to automatically load such a file. Vim script files contain executable code and you do not want to load executable code unconditionally, that's a massive vulnerability. And no, setting the secure option does not help. I use this plugin which makes me first confirm that I want to load the file. From then on it will only automatically load the file if it has not been changed. If the file has changed it will prompt me again.

Try vim-addon-local-vimrc to load a project specific vimrc or vim-ctrlspace to load session infos.

I like monotasking - no plugins eating up screen real estate - so I use [vim-projectionist](https://github.com/tpope/vim-projectionist) and [vim-addon-local-vimrc](https://github.com/MarcWeber/vim-addon-local-vimrc). Projectionist allows me to capture the structure of my project: 'view', 'controller', 'test', 'component', 'feature-x-component', whatever. vim-addon-local-vimrc lets me configure projectionist (and other vim plugins) for my particular project.

Plugin: vim addon local vimrc

This is also not a direct response to your question as I'm not familiar with asycntasks.nvim, but having a build and run functionality is probably the main reason why I wrote confiture.nvim, which is another task launcher plugin (that also aims at being simpler than overseer). The main limitation with the implementation of the build and run of confiture is that the build phase will not be asynchronous. It is sufficient for my workflow though -- if I know the build command will be long, I usually launch it on its own first, which can be asynchronous using confiture (with vim-dispatch under the hood).

It's can also be used from vim to launch custom commands (as is done for example in my other plugin confiture.nvim)

It doesn't answer your question but this is how I do what you described : https://github.com/romainchapou/confiture.nvim

I'm mostly fine with language specific configuration, which I find not too hard to manage in my init.vim, but I rely a lot on project specific commands for building and running projects, so I'll do a shameless plug for my plugin, confiture.nvim, which aims to provide a simple solution for this.