nlsp-settings.nvim VS neoconf.nvim

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.

there is a json schema for nlsp-settings clangd configuration: here In your case, your clangd.json should result like this

import existing settings from vscode, coc.nvim and nlsp-settings.nvim

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

Oh I see now, maybe local nvim lsp configs might help you? https://github.com/tamago324/nlsp-settings.nvim

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 😅).

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.

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

A similar idea for that uses JSON to configure Neovim LSP: nlsp-settings.nvim.

Maybe https://github.com/folke/neoconf.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.

I think this is actually because of neoconf?

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.

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.

If you don’t mind adding a plug-in, neoconf.nvim will let you manage project local lsp settings in a JSON file.

Try https://github.com/folke/neoconf.nvim

There's neoconf by the almighty folke, I am not sure if it is what you are after.

You can find all the details at https://github.com/folke/neoconf.nvim