Replies: 1 comment
-
|
Hi @Kurren123, I'm facing the same issue and wonder if you have come across any fixes? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I set up the following key maps for DAP:
{ "<leader>d", function() require("which-key").show({ keys = "<leader>_d", loop = true}) end, desc = "Debug" }, { "<leader>_db", function() require("dap").toggle_breakpoint() end, desc = "Toggle Breakpoint" }, { "<leader>_dj", function() require("dap").step_over() end, desc = "Step Over" }, -- other dap keymaps, all starting with _dThe problem is when I start debugging and I have the
<leader>dpopup open in hydra mode. If I hitjto step over, the<leader>_dpop 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