lsp-inlayhints.nvim VS null-ls.nvim

Thanks for the reply! I also wanted to make it work with clangd, but it won't. I stumbled upon this issue. Maybe you have enough knowledge to figure this out, I don't know how to set up this compilation database. I installed clangd using Mason, and configured it via lspconfig basically the same way as the guy in the issue I linked did. Also, I'm using the newest nightly.

I don't understand why inlay hints must be implemented in a rust-specific plugin. https://github.com/lvimuser/lsp-inlayhints.nvim exists, has support for inline inlay hints (on a separate branch for now) and works with rust (and should work any language server since inlay hints are part of the spec). Am I missing something?

To use inlay hints in typescript an rust you would need this plugin: https://github.com/lvimuser/lsp-inlayhints.nvim It provides example in the readme on how to setup inlay hints for typescript and rust. For now the master brach has "old" inlay hints implementation but there is a branch that implement new one. And of course you will need nightly version for that for now.

https://github.com/lvimuser/lsp-inlayhints.nvim (Multiple langs)

But it doesn't seem to work. I also tried lvimuser/lsp-inlayhints.nvim with no luck. Any advice of how to properly enable this feature when ocamllsp server is attached? Thank you in advance.

I have inlay hints working in nvim with lvimuser/lsp-inlayhints.nvim, no special configuration other than the LspAttach block from their README. The caveat is that your LSP server has to support inlay hints.

The second one might be https://github.com/lvimuser/lsp-inlayhints.nvim

you can use nvim-lspcofig for LSP support, mason.nvim for installing LSP servers, linters, formatters and debug adapters. nvim-cmp for completions, luasnip for snippets, null-ls for configuring your formatter and linters , lsp-inlayhints for inlay hints.

Inlay hints are available through rust-tools.nvim, or lsp-inlayhints.nvim.

iirc, inlay hints aren't supported by nvim's built-in LSP, but you can get them with the inlay-hints plugin: https://github.com/lvimuser/lsp-inlayhints.nvim (if the LSP for omnisharp also supports them)

you can use nvim then, it has shellcheck for diagnostics and formatting, like in vscode :)

here the link to the config: https://github.com/jose-elias-alvarez/null-ls.nvim/blob/main...

I use a lot of different languages generally and I'm running into issues around formatting. Is there any standard way to use LSP formatting by default and otherwise fallback to specific linter/formatting programs? I believe null-ls is the normal way of dealing with this, but since it's been archived, I'd rather not rely on it.

I've been using pint for formatting php files with null-ls.nvim. Few days ago null-ls.nvim has announced that the plugin will be archived in few months so I started migrating all my formatters and linter from null-ls to efm-langserver. I got other things such as prettier, black, isort, mypy, etc. working but can't get pint to work with php files: If I run pint via efm-langserver, everything is deleted from the buffer, and the saved file is formatted separately. How do I setup efm-langserver correctly to work with pint? Below is my config.yml for pint currently. yaml tools: pint: &pint format-command: "pint --no-interaction --quiet ${INPUT}" format-stdin: false languages: php: - <<: *pint Thank you.

Because null-ls.nvim & mason.nvim together do everything I wanted CoC for

There is a good answer. I think you know lua and neovim config enough to pick things that you need. If you need a short answer, null-ls is the way.