lvimuser

> actually I'm pulling the latest source code from vim repo and built on myself. Did you also apply the patch? `wget https://patch-diff.githubusercontent.com/raw/neovim/neovim/pull/20130.patch && git apply 20130.patch`

> With clangd, I observe that in the case of nested function call, I see that only inner call has inlay-hints and not the outer call. > Can this be...

Can you try the other branch?

This seems to a problem with `numToStr/Comment.nvim`; same behavior with builtin codelens. The extmarks do not get pushed to the line below when using macros, visual block or `vim-visual-multi`. As...

> get `nvim_buf_get_extmarks` > provide `nvim_buf_set_extmarks` > clear `nvim_buf_clear_namespace` or `nvim_buf_del_extmark` > resolve callback(s). It's a `clear` followed by a `set`, or you can save the `id` and call `set_extmarks`...

> My plugin A [...], and my plugin B need to search it again and append on the result of plugin A and so on...... But what if plugin A...

> Please don't wrap built-in functions. If it's not explicitly documented that they're designed to do that, it is not supported. What I meant is you can write your own...

> > No idea how to test this. > > You can have a look in ./test/functional/plugin/lsp_spec.lua at existing test cases. There are some where the handler is called directly....

Does increasing [fetching_timeout](https://github.com/hrsh7th/nvim-cmp/blob/main/doc/cmp.txt#L400-L405) help?

Should be fixed after https://github.com/folke/which-key.nvim/commit/36fdfe833207c120997c669a2c51060813f2f8a7 Can you try that version?