I'm in the second month of using lsp, and I'm really enjoying it. Just want to say thanks again, before I get into what I'm experiencing now. (:
It seems that lsp and CIDER are fighting over my minibuffer - lsp saying 'invalid arity, you haven't passed all the args', and CIDER saying 'here's the eldoc you need to know what arguments to pass'
Anyone experienced similar? What possible interventions are there? I imagine this is driven by lsp calling message when the cursor is on a line with a linting error, which seems like a good idea, but it's stomping my eldoc. 🙂
Glad you are liking it! most people simply do https://github.com/ericdallo/dotfiles/blob/fd608ccd5e5a9714893754704963a0fd7cd24a49/.config/doom/config.el#L55, as lsp is more precise/faster/non repl dependent for that feature
Thanks. That's an interesting idea, but with or without that I still don't see the arglist in my minibuffer:
Maybe if the [invalid arity] message included the arglist, that would be helpful?
that happens because your emacs using the minibuffer to show both diagnostics and arity, you should probably rely on a different package to show diagnostics, minibuffer is not a good place for that IMO, I use flycheck but there is flymake as well
actually, this is the only feature I use from lsp-ui, the errors close to where it happens:
oh yeah, that screenshot looks great, how do I configure it that way? (tell me to rtfm if you want) 🙂
https://github.com/ericdallo/dotfiles/blob/fd608ccd5e5a9714893754704963a0fd7cd24a49/.config/doom/config.el#L182-L187 should do it, lsp-ui has lots of "too much for most people's taste" UI features, but that one is gold
that's why I disable others
Thank you! I've started down this path, I'm excited.