nvim-projectconfig VS vim-localvimrc

This plugin could be helpful: https://github.com/windwp/nvim-projectconfig/

My original use-case was, that I wanted to have a lua file per project which for example sets up the dap-configurations since not all projects need the same configurations. I found nvim-projectconfig but I'd need to create a file for each project but I don't want them to be always in my runtime.

Another way is to add nvim config to each project using this plugin: https://github.com/windwp/nvim-projectconfig. Or just search for "vim project based config" in some search engine.

Or safer than .nvimrc.. use plugin nvim-projectconfig

why should one use this over https://github.com/windwp/nvim-projectconfig which is mostly in lua

Plugin: nvim project config

https://github.com/windwp/nvim-projectconfig lol why you need to put projectconfig to same folder with yourcode. you can put it in your .config/nvim/projects and only you can see it and you don't care anything about security.

this is a reason i wrote that plugin https://github.com/windwp/nvim-projectconfig

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.