You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is when I start debugging and I have the <leader>d popup open in hydra mode. If I hit j to step over, the <leader>_d pop up opens again due to the loop = true. However sometimes it takes a second for a line of code to execute, so the neovim UI doesn't show that we're on the next line of code until I actually close which-key with <esc>.
In other words: Is there a way to do hydra mode without blocking neovim ui?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I set up the following key maps for DAP:
The problem is when I start debugging and I have the
<leader>d
popup open in hydra mode. If I hitj
to step over, the<leader>_d
pop up opens again due to theloop = true
. However sometimes it takes a second for a line of code to execute, so the neovim UI doesn't show that we're on the next line of code until I actually close which-key with<esc>
.In other words: Is there a way to do hydra mode without blocking neovim ui?
Beta Was this translation helpful? Give feedback.
All reactions