nvim-config-local
project-settings.nvim
nvim-config-local | project-settings.nvim | |
---|---|---|
6 | 5 | |
134 | 16 | |
- | - | |
5.0 | 0.0 | |
11 months ago | almost 2 years ago | |
Lua | Lua | |
MIT License | 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.
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
project-settings.nvim
-
I didn't know before that having multiple Neovim instances is bad
That command actually uses project-settings.nvim to setup all the things, not just lsp.
- Run Python venv from nvim
-
Some questions about Lua plugin development
If it helps, you can take a look at this little plugin I made: project-settings.nvim.
-
Using project-settings.nvim to call language servers
project-settings.nvim is a plugin I created to handle some unique scenarios I faced in a couple of projects. It allows you to reuse a lua function across multiple projects, and pass arguments to it using a json file. (I know one could just use an exrc file, but I don't like them).
-
How do y'all feel about handling project local settings using a json file?
Once again I found myself turning a piece of my config into a plugin. This time around it is the project local settings: project-settings.nvim
What are some alternatives?
direnv.vim - vim plugin for direnv support
workspaces.nvim - a simple plugin to manage workspace directories in neovim
IDE.nvim - IDE-Like support for NeoVim
editorconfig-vim - EditorConfig plugin for Vim
confiture.nvim - A neovim lua plugin to save and launch project specific commands.
plugin-template.nvim - A template to create Neovim plugins written in Lua
exrc.nvim - Secure Project Local Config for Neovim
nvim - One editor to roll them all. (GotoDef FindRef Completion Snippet Format Lint Refactor Test Debug Repl Task)
lsp-zero.nvim - A starting point to setup some lsp related features in neovim.
penvim - Project's root directory and documents Indentation detector with project based config loader
persistence.nvim - 💾 Simple session management for Neovim
flow.nvim - A neovim plugin that lets you build custom commands to automate parts of your development workflow