Change:
// When no expression available fallback to editor hover this.showEditorHover(position, focus); } <ins> } else { this.showEditorHover(position, focus); </ins> } }

Discussion:
Sometimes I leave the debugger running when editing code and making changes. The one thing which fails to work during this period is triggering hover from a keybinding (ctrl/cmd+k, ctrl/cmd + i). Whenever I trigger this over a red squiggly line nothing happens. I understand this is because the debugger overrides that keybinding when running but 90% of the time it's replaced with nothing. Is it possible to fall back through to the normal hover action if im not on a line currently being inspected? This must be possible because mouse hover does exactly this. This seems to be the UX with mouse hover: a breakpoint has triggered I get the debug info on hover. a breakpoint hasn't triggered the hover falls back to normal hover information Triggering hover with keybindings: a breakpoint has triggered I get the debug info on hover. a breakpoint hasn't triggered nothing happens. This issue is asking for the keyboard shortcut (ctrl/cmd+k, ctrl/cmd + i) to match up with the mouse hover.
Holding while hovering in a debug session will have VS Code show the "non-debugger" hover. I think it's a bug/polish item that we should automatically fall back to that if evaluating the hovered expression in the debugger does not returning anything. Code pointer to where we trigger the standard hover: Code pointer to the 'no-op' path that triggers if nothing is returned by the DA
Regarding the keybinding, there are two "Show hover" commands. "Debug: Show Hover" won't do anything when not at a breakpoint. You should set different keybindings, or use when clauses to run the right one, if that's what you are expecting.
is this still considered to be a valid issue and work needs to be done ? I can open a PR for this if this is still legit requirement/bug
I don't believe this issue has been addressed yet and is still valid
Great , upon investigation I notice that the UX you've mentioned here When a breakpoint has triggered I get the debug info on hover. When a breakpoint hasn't triggered the hover falls back to normal hover information doesn't seem to be the case. When I mouse over a line (containing squiggly expression/ any line for that matter) which is not at a break point nothing happens.

I get normal hover information upon pressing Unless I'm missing something or misunderstood the issue , I notice the behaviour is same for both keyboard and mouse commands. So both the actions yield nothing to me. However , what and mentioned sounds like a valid solution to the problem
I can’t reproduce it now but I’m sure in some cases it was showing the normal hover without needing to press Alt (when debugger was on) In response to yes that is true that the other command can be used but it’s quite un-ergonomic. Sometimes I don’t know the debugger is running because I spend all day using it on and off. So now I have to think which command/keybinding to use for the same action that usually comes naturally to me. It also feels like broken UX when info about a symbol stops showing anything (not even a “no debug info here”) so this should be addressed regardless. I do like suggestion of falling back to a normal hover if that’s possible as that would help with productivity, rather than pushing all your users to create workarounds.
I also like connor's suggestion, that's why I left it open, the workaround is for before it gets fixed. You can have a single keyboard shortcut that runs a different command based on
OK I can reproduce this now. This is debugging VSCode itself on Windows. In this gif i am trying ctrl + K, ctrl + I (which usually reveals the hover). Nothing happens. But when I hover over with the mouse (I am not pressing ) i get info. !
I too was able to reproduce it some time ago , I was working on the fix , hopefully will be able to submit a PR soon
Thank you for this ill look forward to trying it out!
the hotkey still does not display hover for me while in debug mode:
verification-found means the issue can be reopened. This is working for me though, can you explain what you are debugging and hovering, or call me to show?
Thanks this still doesn't show the editor hover when the keybinding is used, when not at a breakpoint. cc if you want to work on it again.
Hey guys , Sure I can check . Can one of you attach a reproducible screen recording ? Does it not work under any specific circumstance ?

Thanks
Just these steps Start debugging, but don't stop at any breakpoint Run the keybinding for the command The hover does not appear
Thanks . I will look into it this week