use native lsp inline virtual text on neovim nightly

[ClSlaid]

Feature description

NeoVim nightly just got native inlay virtual text support. 0.10 branch now could get rid of lsp-inlayhints.nvim.

showcase with rust

Additional information

No response

[fecet]

Can we also get rid of lsp_signature, it's the reason of many delay of nvim-cmp. However most python lsp (I primarily use python) doesn't support inlay hint, maybe change to pylyzer?

[charliie-dev]

Upvote for removing lsp-inlayhints.nvim and lsp_signature in 0.10 branch. (Personally I don't use lsp signature's functionality)
I'm not sure about pylyzer tho, never tried it before.

[ayamir]

Can we also get rid of lsp_signature, it's the reason of many delay of nvim-cmp. However most python lsp (I primarily use python) doesn't support inlay hint, maybe change to pylyzer?

IMO inlay hint isn't so important to make us replace pylsp with pylyzer which isn't tried and tested very well.

[fecet]

Personally, I would like to give pylyzer a try because I often experience delays with nvim-cmp and gd when browsing large files, perhaps I will create a PR for this.
However, is there any way to test the differences between LSPs to check if Pylyzer is better (or worse)?

Edit: pylyzer doesn't support local package so it may not avaliable now... But I just found https://github.com/jbradaric/pyright-inlay-hints, maybe we can try this fork

[Jint-lzxy]

Can we also get rid of lsp_signature, it's the reason of many delay of nvim-cmp.

IMHO We should keep lsp_signature b/c we need this for languages that require information related to function signatures (e.g., languages that support function overloading like C++). This delay is actually an upstream issue.

However, is there any way to test the differences between LSPs to check if Pylyzer is better (or worse)?

Check if it supports maximum server capabilities (subsection TextDocumentClientCapabilities).

[vollowx]

Maybe have a look at this as a ref.

[charliie-dev]

Maybe have a look at this as a ref.

I think it's not a bad idea to remove lsp_signature if u got free time and looking for max nvim startup speed; however, then we will need to config each language servers, which would be quite a hustle for neovim new comers to config their own language servers.

To avoid issue overflow, I think it's better to keep the nvim config more on the sensible side.

[charliie-dev]

This feature is already implement in https://github.com/ayamir/nvimdots/tree/0.10 branch, closing this issue if no further discussion.

[fecet]

This feature is already implement in https://github.com/ayamir/nvimdots/tree/0.10 branch

This is implement by https://github.com/lvimuser/lsp-inlayhints.nvim, is there any reasonn to use it over native inlay support?

[charliie-dev]

This is implement by lvimuser/lsp-inlayhints.nvim, is there any reason to use it over native inlay support?

Sorry, missed that. reopen the issue.

[vollowx]

Note that the native API has recently changed at this commit