neoconf.nvim
nlsp-settings.nvim
Our great sponsors
neoconf.nvim | nlsp-settings.nvim | |
---|---|---|
10 | 10 | |
599 | 296 | |
- | - | |
8.6 | 8.5 | |
5 days ago | 4 days ago | |
Lua | Lua | |
Apache License 2.0 | 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.
neoconf.nvim
-
What IDEA or Vscode feature/function you want to have in neovim eco-system?
Maybe https://github.com/folke/neoconf.nvim
-
New Plugin: Gitlab.nvim
One suggestion: It looks like your plugin's config makes assumptions about all projects (e.g. main branch name). It might be a good idea to support something like neoconf.nvim to configure the plugin on a per-project basis.
-
Is this LSP configuration proper or is it a sloppy hack?
I think this is actually because of neoconf?
-
Volar with VueJS 3
I have this working in a way that's comparable to how you would configure the VSCode extension.First, you need to install folke/neoconf.nvim and call it's setup function before you setup mason or your lsp-config.
-
How to set up local project-specific configurations?
A limited class of settings can be managed per-project with folke/neoconf.nvim with a primary emphasis on LSP settings, so definitely give it a look. I think it's the cleanest approach until the exrc-replacement lands in stable.
-
neovim lsp rust-analyzer, some projects require special targets+features and others dont.. how to handle projects?
If you donβt mind adding a plug-in, neoconf.nvim will let you manage project local lsp settings in a JSON file.
-
Using local lsp configs to set up lsp config
Try https://github.com/folke/neoconf.nvim
-
Local configs
There's neoconf by the almighty folke, I am not sure if it is what you are after.
-
neoconf.nvim: a Neovim plugin to manage global and project-local settings
You can find all the details at https://github.com/folke/neoconf.nvim
nlsp-settings.nvim
-
What SQL formatter do you use? What can give you Intellij like formatting for SQL?
I also use sql-language-server for completion. It works for me with a .sqlrc.json config file, which allows me to change database config based on parent directory. I have not been able to configure sqlls with nlsp-settings for some reason.
-
Setting up a local LSP config for clangd using nlspsettings
there is a json schema for nlsp-settings clangd configuration: here In your case, your clangd.json should result like this
-
neoconf.nvim: a Neovim plugin to manage global and project-local settings
import existing settings from vscode, coc.nvim and nlsp-settings.nvim
-
nlsp_settings: Root dir for pyright/jedi-ls
Couldn't figure out from the nlsp_settings neovim plugin ( https://github.com/tamago324/nlsp-settings.nvim ), how to set the "Root dir" or the "Root pattern" property. I am using the jedi-language-server for lsp but would switch to pyright if this problem could be fixed only in that one. Did anyone run into this problem before and can help me? tnx
-
Managing multiple incompatible toolchains/compilers?
Oh I see now, maybe local nvim lsp configs might help you? https://github.com/tamago324/nlsp-settings.nvim
-
I'm not getting null-ls autocompletions for JSX unless tsserver is required
I'm sure there are low level configuration you can do to configure them, like your snippet above, I suggest you to try nlsp-settings.nvim to configure lsp using json (like in vsc*de π ).
-
Nvim config for working with programs running in docker containers
And then with nlsp-settings you can add a config like "extraPaths" or something like that that gives the pylsp or pyright extra places to look for libraries. With that done it works, the thing is you would have config in the compose file that is specific to you only.
-
How to get completion in commonly used JSON files like package.json, tsconfig.json, prettierrc.json etc?
I think you would need to pass in a schema to jsonls for that. Check out this plugin: https://github.com/tamago324/nlsp-settings.nvim/ to see how a schema would be shaped like
-
Defaults.nvim: A minimal but complete init.lua template
A similar idea for that uses JSON to configure Neovim LSP: nlsp-settings.nvim.
- nlsp-settings: A plugin for setting Neovim LSP with JSON files
What are some alternatives?
neodev.nvim - π» Neovim setup for init.lua and plugin development with full signature help, docs and completion for the nvim lua API.
nvim-lspconfig - Quickstart configs for Nvim LSP
gitlab.nvim - Create, review, and manage Gitlab reources without leaving Neovim
lspkind.nvim - vscode-like pictograms for neovim lsp completion items
vim-arduino - Vim plugin for compiling and uploading arduino sketches
SchemaStore.nvim - π JSON schemas for Neovim
vim-submode - Vim plugin: Create your own submodes
lspkind-nvim - vscode-like pictograms for neovim lsp completion items [Moved to: https://github.com/onsails/lspkind.nvim]
vim-mergetool - :cake: Efficient way of using Vim as a Git mergetool
kickstart.nvim - A launch point for your personal nvim configuration
Visual Studio Code - Visual Studio Code
defaults.nvim - A small, documented, and featureful neovim starter config [Moved to: https://github.com/nvim-lua/kickstart.nvim]