confiture.nvim
A neovim lua plugin to save and launch project specific commands. (by romainchapou)
nvim-config-local
Secure load local config files for neovim (by klen)
Our great sponsors
confiture.nvim | nvim-config-local | |
---|---|---|
5 | 6 | |
16 | 134 | |
- | - | |
4.7 | 5.0 | |
8 months ago | 11 months ago | |
Lua | Lua | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
confiture.nvim
Posts with mentions or reviews of confiture.nvim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-05.
-
Build and run in one task using asynctasks.vim
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).
-
If you are not satisfied with the terminal emulator of Neovim, or preferred the one of Vim, you should checkout nostalgic-term.nvim
It's can also be used from vim to launch custom commands (as is done for example in my other plugin confiture.nvim)
-
How does <CTRL-ENTER> run my python scripts?
It doesn't answer your question but this is how I do what you described : https://github.com/romainchapou/confiture.nvim
-
How do you handle project specific configuration?
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.
- confiture.nvim: a simple way to save and launch your project specific commands
nvim-config-local
Posts with mentions or reviews of nvim-config-local.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-04.
-
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?
When comparing confiture.nvim and nvim-config-local you can also consider the following projects:
exrc.vim - Local vimrc files
direnv.vim - vim plugin for direnv support
project-settings.nvim - Manage project local settings using a json file.
vim-addon-local-vimrc - kiss local vimrc with hash protection
IDE.nvim - IDE-Like support for NeoVim
exrc.nvim - Secure Project Local Config for Neovim
overseer.nvim - A task runner and job management plugin for Neovim
lsp-zero.nvim - A starting point to setup some lsp related features in neovim.
compit - Makes compiling and running your code from inside NeoVim enjoyable.
persistence.nvim - 💾 Simple session management for Neovim
confiture.nvim vs exrc.vim
nvim-config-local vs direnv.vim
confiture.nvim vs direnv.vim
nvim-config-local vs project-settings.nvim
confiture.nvim vs vim-addon-local-vimrc
nvim-config-local vs IDE.nvim
confiture.nvim vs IDE.nvim
nvim-config-local vs exrc.nvim
confiture.nvim vs overseer.nvim
nvim-config-local vs lsp-zero.nvim
confiture.nvim vs compit
nvim-config-local vs persistence.nvim