vim-dotenv VS vim-localvimrc

I use nvim-dap and nvim-dap-go for debugging microservices and Go based tests on a daily basis. For loading .env files, i have a keybind set up to run vim-dotenv (https://github.com/tpope/vim-dotenv). If dap is supposed to autoload env files, I've never read about it. :-)

I take it you read https://github.com/tpope/vim-dotenv?

Using environment vars should be good : https://github.com/tpope/vim-dotenv is a plugin able to read .env files. you can also run vim like this PROJECT=myproject SPACES=4 vim but I don't think this will do the trick for you. Finally if it is only a indent/end char/... issue, you can check https://editorconfig.org/

A big part of 'project awareness' implies (to me at least!) that a project is organized in some meaningful way: test/view/model/service/domain files all relate to one another by their naming conventions and location in the project tree.When I start/join a project I look for documentation of the project's structure (or document it myself!). Then for vim:- use https://github.com/embear/vim-localvimrc - drop a .vimrc in the project so I can tweak vim to suit the project.

Something like Localvimrc?

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

Is vim modeline a good way to do it? What do you think about that solution: https://github.com/embear/vim-localvimrc?

This is pretty much the last one, but with available commands. One I find particularly useful is LocalVimRCCleanup. I'm not sure how common of a use-case this is, but AutoSource stores the hashes of each file you approved, and a common command I run while testing is rm ~/.autosource_hashdir/* :p

Nice video. I have a similar approach for isolating project specific commands and configurations. I may borrow your idea for a project specific menu to run tasks. For a project dedicated vimrc I use embear/vim-localvimrc for a few years because it has auto discovery and auto change directory for a project, and require confirmation for loading the vimrc file.