I don't think we have a way to disable hovers for keywords. I can recommend setting the hover time to some 1500 ms. (I have 1300 ms). That will allow you to trigger the hovers more at will. The default is way too quick for me and I find myself navigating the with the mouse to avoid hovers.

btw, you should only get the implementation if you press cmd while hovering.

Ah ok, the implementation was then a fluke 🙂

Is this something that merits a setting? Or perhaps disabling altogether? Not sure I see the value, but perhaps there's users of re-frame that want that.

Come to think of it, see if it can be configured in clojure-lsp

We could probably filter out a lot of useless hovers by just checking the return value against the hover-text. If they are basically the same we can just not return the hover

We just will have to define ”basically” 😃 I also think this might be a signal to the developer to add docs to their functions, so not sure it is a good heuristic. This particular one looks a bit strange in that it presents a symbol for what is a keyword. Might be a bug in clojure-lsp? cc: @UKFSJSM38

it's espected, but we may want to change to not return hover for simple-keywords

more discussion about this https://clojurians.slack.com/archives/CPABC1H61/p1647269696331829

TLDR, even disabling for keywords, I still think hovers are agressive in Calva, it's not the first or second time someone complain to me about Calva showing hovers because the mouse is on a function or var or something like that while user is reading a code

I never had problems with it. People should probably disable mouse hovers or increase the delay and use the “show hover” command on a hotkey

Yeah, I don’t think it’s really Calva-related, just VS Code.

There's some connected issue with hovers and evaluation results though - if you show them on hotkey, you then basically can't scroll them as they disappear on mouse move. This might be an ordering issue, eg the evaluation results should probably above the Clojure docs…

Issue from 2016, now closed :/ https://github.com/microsoft/vscode/issues/15667

I’ve also noticed that results are below other hover info. @U0ETXRFEW Can we make results appear at the top?

switching the order around isn’t usually hard, I just played a lot with the hover provider. But I somehow can’t find where the eval hover comes from 🙂 Doesn’t seem to be set in the hoverProvider

Let's bring the results to the top. Or at least try to. Please create an issue for it.

Usually result of stale LSP, try "Developer: reload window"

I'm working on a version of Calva where it will be possible to restart clojure-lsp w/o reloading the entire window. Here's a VSIX: https://19430-125431277-gh.circle-artifacts.com/0/tmp/artifacts/calva-2.0.254-1592-stop-start-clojure-lsp-5fcf9853.vsix (Early build, but it seems to work when I test it.)

PR: https://github.com/BetterThanTomorrow/calva/pull/1595

Mentioning this hover timer at work has gained me a lot of gratitude.

"editor.snippetSuggestions": "top" //will be better once I'm done with the lsp/repl completion merge
"calva.prettyPrintingOptions"

Funny, I also thought about the pretty printing options. Might make a good video on its own. There are a bit of details around it that is good to know about.

I am planning to go over https://www.reddit.com/r/vscode/comments/pqfpnc/i_realized_why_i_was_annoyed_with_vscode_and/ tomorrow

Especially the “accept on enter” thing

It's happening all the time: parameters passsed in maps as keywords: :foo-id. Destructure inside a let or a function as foo-id. Hit enter, autocomplete to :foo-id again :/

Agreed, I feel like vscode’s default hover time is frustratingly short. Increasing it was a huge improvement.

To me it looks like that redditor should be using Notepad. 😃

Yeah, I agree with the first comment on that post: give me as much help as possible, I’m not a professional compiler 😛

Hello. Please create an issue and include example code that can be used to reproduce this. It sounds like maybe the breakpoint finding logic is having some issue.

To see if we have introduced the breakpoint finding problem recently, please also also try with Calva 2.0.249 and see if that version behaves correctly.