BUG: After exiting debug mode, x is no longer working in NORMAL mode.

[bokonist]

Did you check docs and existing issues?

• I have read all the docs.
• I have searched the existing issues.

Neovim version (nvim -v)

0.11.1

Operating system/version

OS: Manjaro Linux x86_64 Kernel: 6.6.88-1-MANJARO

Describe the bug

x to delete the char under the cursor is no longer working in normal mode after debug mode is exited. after debug mode is exited, it's not falling back to the original behavior.

Steps To Reproduce

1. Enter debug mode (:lua require("debugmaster").mode.toggle())
2. exit debug mode (:lua require("debugmaster").mode.toggle())
3. use x to delete character under cursor. does not work.

Expected Behavior

go back to default behavior of x

I suspect this is because of this keymap inside debug mode:
x Execute last yanked or deleted text in the repl

Repro (Ignore if not applicable or if the issue is easily reproducible.)

-- set stdpaths to the current directory
local initlua_root = vim.fn.fnamemodify(debug.getinfo(1).short_src, ":p:h")
for _, name in ipairs { "config", "data", "state", "cache" } do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = initlua_root .. "/" .. name
end

-- bootstrap lazy
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.uv.fs_stat(lazypath) then
  local lazyrepo = "https://github.com/folke/lazy.nvim.git"
  vim.fn.system({ "git", "clone", "--filter=blob:none", "--branch=stable", lazyrepo, lazypath })
end
vim.opt.rtp:prepend(lazypath)


vim.g.mapleader = " "
require("lazy").setup({
  spec = {
      {
        "mfussenegger/nvim-dap",
        config = function()
          local dap = require("dap")
          -- Configure your debug adapters here
          -- https://github.com/mfussenegger/nvim-dap/blob/master/doc/dap.txt
        end,
      },
      {
        "miroshQa/debugmaster.nvim",
        config = function()
          local dm = require("debugmaster")
          vim.keymap.set({ "n", "v" }, "<leader>d", dm.mode.toggle, { nowait = true })
          vim.keymap.set("t", "<C-/>", "<C-\\><C-n>", { desc = "Exit terminal mode" })
        end
      }
  },
})

[MironPascalCaseFan]

Strange, can't reproduce the issue—'x' restores properly for me. Make sure you've updated the plugin to the latest version. If it still persists, I’d suggest you attach a screen recording so I can understand what else could cause this bug. (You can pretty easily record your screen using OBS, then drag and drop the video here.)

[bokonist]

ah, probably some keymap conflicts on my end then, if you can't reproduce it. I don't see a conflict but the issue still persists.

I've just remapped x to y and the issue isn't so annoying anymore. thanks for the plugin!

dm.keys.get("x").key = "y" -- remap x key in debug mode to y

lmk if you still need a video, the issue is pretty much exactly as described, i need to search how to display key presses on screen if you need a vid.

[Kurren123]

I can confirm the same bug. Also the cursor turns green when entering debug mode but doesn't turn back to it's usual colour after leaving debug mode. OS: Windows 11. Using the latest version of neovim and debugmaster.

Edit: Found the offending plugin. It was hardtime.nvim. The green cursor thing I have yet to sort out however.

[MironPascalCaseFan]

@Kurren123

1. Does only the "x" key cause this bug? Very interesting why it happens only with this key.
2. Can you try other terminal emulators? Does it (green cursor thing) happen with bare-bones Neovim with only debug plugins installed?

Also, I recently discovered that one-small-step-for-vimkind integration doesn’t work on Windows, so I want to warn you about this as a Windows user. (UPD: Fixed with the last commit)

UPD: I tried it on windows and I also have the cursor not turning back issue in wezterm. In windows terminal it doesn't turn green for me at all

[MironPascalCaseFan]

@Kurren123 try to put something like this in your nvim config before requiring debugmaster (to fix the cursor issue):

vim.go.guicursor = "n-v-sm:block,i-t-ci-ve-c:ver25,r-cr-o:hor20,a:Cursor"

You can also then change Cursor highlight group:

vim.api.nvim_set_hl(0, "Cursor", { bg = "#FFA500" })

[agokule]

In case other people have this problem where hardtime.nvim is interfering and they end up here in the future, a good workaround for this would to toggle hardtime before toggling debugmaster. For example, i have this as the callback for my toggling keymap:

function()
    vim.cmd.Hardtime('toggle')
    require("debugmaster").mode.toggle()
end

this fixed my issue in which the "x" and "c" keys would not work after going to debug mode. In general, I guess you have to temporarily disable these kinds of plugins before debug mode and re-enable them after. This should probably be mentioned in the readme.