How to change the default mapping of <CR> on dap-repl?

[nyngwang]

If I press <CR> on dap-repl buffer then I will get a warning like this:

DAP No action possible on: Type 'dlv help' for list of commands.

then I found that it is a result of the underlying command:

lua require('dap.ui').trigger_actions({ mode = 'first' })

which is set by default in both

nvim-dap/lua/dap/ui/widgets.lua

Lines 10 to 11 in 700a3c7

	api.nvim_buf_set_keymap(
	buf, "n", "<CR>", "<Cmd>lua require('dap.ui').trigger_actions({ mode = 'first' })<CR>", {})

and

nvim-dap/lua/dap/repl.lua

Line 32 in a9f21a2

api.nvim_buf_set_keymap(buf, 'n', '<CR>', "<Cmd>lua require('dap.ui').trigger_actions({ mode = 'first' })<CR>", {})

Since I already have a normal map for <CR>, I would like to know how to change/disable these mappings by default.

---

UPDATE: I came across an issue where you shared an example usage of dap.listeners.after by your dotfiles. While that seems the most related to my problem here, I still don't know how to override the default <CR> keymap given this info.

[mfussenegger]

With 43695d2 you should be able to setup a FileType autocmd for dap-repl to override/remove the keymap.

vim.api.nvim_create_autocmd('FileType', {
  pattern = 'dap-repl',
  callback = function(args)
    vim.keymap.del('n', '<CR>', { buffer = args.buf })
  end
})

[nyngwang]

Thank you for supporting this!

[nyngwang]

@mfussenegger It seems that this FileType autocmd can work only after first calling dap.continue(). It doesn't work after the buffer got updated after calling either dap.step_into/out/over().

update: Just resolved this problem by using WinEnter instead. I guess that the vim.bo.filetype is not always set upon the FileType event, or maybe the default mapping <CR> is added back by some other autocmd.

vim.api.nvim_create_autocmd({ 'WinEnter' }, {
  pattern = '*',
  callback = function ()
    if vim.bo.filetype == 'dap-repl' then
      pcall(vim.keymap.del, 'n', '<CR>', { buffer = vim.api.nvim_get_current_buf() })
    end
  end
})