Could you share a print of what you are seeing on completion and what you expect to see?

Sure 1 second

I'll create a minimal example for reproduction

This is what I see when in the cmp completion dialog which uses the lsp completioin source. The source file is the file where I used import-vars.

This is what I see when I used the plugin I mentioned above. I haven't checked where exactly they get this info from, I'll take a look.

Here's what I see on hover . The source file is the file where the var os original def'd.

In the completion (first screenshot) I would expect seeing the docstring and arity information.

Thanks for the detailed info, yeah, could be something on server on client, kinda hard to tell, but if you manage to make a simple repro project with that I can try and confirm where is the bug

Sure, I'll do that. Btw, the plugin apparently - as the name suggest - simply https://github.com/hrsh7th/cmp-nvim-lsp-signature-help/blob/3d8912ebeb56e5ae08ef0906e3a54de1c66b92f1/lua/cmp_nvim_lsp_signature_help/init.lua#L62-L75, so clojure-lsp is definitely making the info available there. The question now is whether the completion problem is server or client as you mentioned.

Hum, yeah, fut from what you are seeing the completion popup I'd guess it's server's fault

better late than never!

I am not sure what's the culprit, if I remove markdown mode from the picture it works (no error, but I get no doc popup), but it could just be a side-effect

it's with eglot 1.14 only 1.13 works

Sorry, I don't have context o about eglot, but I use company-quickhelp with clojure-lsp and works all the time, so it's probably a eglot thing indeed I think

I was wondering if it could be related to the server response maybe, but I ll wait on eglot maintainer to look at it more

I don't think it's server response otherwise we could probably repro in other packages/editors, but you can can confirm checking the <https://clojure-lsp.io/troubleshooting/#client-server-log%7Cclient&lt;-&gt;server logs>, and check what server returns after you trigger the completion

it's an eglot bug 🙂

https://github.com/joaotavora/eglot/discussions/1202#discussioncomment-5544273

Glad you found it :)

he did!