[enhancement] stop nvimgdb_config_override when in the debug console

[sakhnik]

[enhancement] stop nvimgdb_config_override when in the debug console

[Narice]

I came back to the plugin today and yes! this works out of the box
Don't really know why it didn't work at the time!

[sakhnik]

@Narice, I can't understand the issue yet. Could you please provide your configuration and the steps to reproduce the problem?

[Narice]

Sorry for the late reply but here is what is happening.
in my .vimrc, I have put the code that is in the README.md for nvimgdb_config_override.
Thus, I have 's' mapped to 'step'.
But, when I do :GdbStart, I have to enter 'start' in the gdb console to start the process
But, as I have 's' mapped to 'step', I can't enter the 's' of 'start' without triggering the step command.
So I can't write 'start' in an intuitive fashion in the console.

Step to reproduce:

• Put the code mentioned in the README.md into a .vimrc
• Start the debug tab
• Try to enter start or any command including any letter used in the nvimgdb_config_override option in the gdb console

[sakhnik]

I see what's going on now, thanks! Let me think how to fix it.

[sakhnik]

It turns out it's already possible to suppress the keymaps in the terminal window. So going to update the README.

[Narice]

Sorry to bother but I don't really see how what you added in the readme helps.
It seems I didn't understand the solution
I'll try to work it out in the meantime but I'm not sure I'll succeed
just copying what you wrote doesn't work out of the box, I'm surely missing something

[sakhnik]

It should work out of the box now. We started from the keys like s triggering a GDB command step in the debugger window. However, if an (almost) empty hook function set_tkeymaps is specified, the plugin won't define normal keymaps in the terminal window.
It tried the config and it works for me.