exrc.vim
nvim-config-local
exrc.vim | nvim-config-local | |
---|---|---|
9 | 6 | |
19 | 134 | |
- | - | |
1.8 | 5.0 | |
over 2 years ago | 11 months ago | |
Vim Script | Lua | |
The Unlicense | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
exrc.vim
-
How do you handle project specific configuration?
exrc can enable untrusted arbitrary execution. See https://github.com/ii14/exrc.vim that tries to mitigate this.
- Multiple instances of Vim.
-
Best plug-in for per project config changes and compilation shortcut
'exrc' option or https://github.com/ii14/exrc.vim
- Resources on project specific vim setup
-
Are there any plugins available to fix exrc not working when you use init.lua?
Yeah, here's my plugin that does that: https://github.com/ii14/exrc.vim
-
HOW DO I MAKE A PROJECT SYSTEM
:set exrc and and create .exrc file in your project directory with your project settings, or use a plugin like https://github.com/ii14/exrc.vim or https://github.com/jenterkin/vim-autosource
- Lua-based local config plug-in?
-
Feedback on a small vim plugin
I did basically the same thing, but without recursive lookup: https://github.com/ii14/exrc.vim
-
Running Tasks in Vim
https://github.com/ii14/exrc.vim for local vimrc. Basically a reimplementation of the 'exrc' option that keeps track of file hashes, so you don't evaluate anything malicious, without the limitations of 'secure' option.
nvim-config-local
-
Using LazyVim and Mason.nvim LSP manager. How do I add arguments to the clangd or and LSP?
it's been undeprecated recently, but if you would prefer to use a plugin, I use this one
-
[Question] Plugin which sources lua files from a directory depending on project?
The next version of neovim (and currently, nightly) re-enables support for exec, which sounds close to what you want. In the meantime check out https://github.com/klen/nvim-config-local. These both do a single file, but once you're running some code it's easy enough to get that file to source more.
- How to configure telescope (or any other plugin) per project?
-
How do you handle project specific configuration?
I just use nvim-config-local, which is basically just souped up :h 'exrc'. And then from there I typically set makeprg and a custom "run" command if I want, along with any other settings I might want in the project. I tried using some custom runner type plugins in the past but I think this method has provided me with the most flexibility, and I don't have to learn anything new because it's just the same as what i do in my init.lua.
-
How do y'all feel about handling project local settings using a json file?
I took inspiration from nvim-config-local and added an integrity check, to force the user to review the settings file at least once. It's on by default, but is optional. The file can be safe to use if you don't expose any option that allows for arbitrary code execution.
-
Manage project local settings for a language server with lsp-zero
nvim-config-local
What are some alternatives?
direnv - unclutter your .profile
direnv.vim - vim plugin for direnv support
vim-projectionist - projectionist.vim: Granular project configuration
project-settings.nvim - Manage project local settings using a json file.
vim-autosource - Manage Vim configuration for projects.
IDE.nvim - IDE-Like support for NeoVim
neovim - Vim-fork focused on extensibility and usability
confiture.nvim - A neovim lua plugin to save and launch project specific commands.
localvimrc - load subdirectory specific vimrc files
exrc.nvim - Secure Project Local Config for Neovim
vim-localvimrc - Search local vimrc files (".lvimrc") in the tree (root dir up to current dir) and load them.
lsp-zero.nvim - A starting point to setup some lsp related features in neovim.