Failed to bind ctrl-m

[JacksonHub2]

Description of the problem or steps to reproduce

When adding keybindings with the Ctrl-m, it seems micro failed to phrase to execute:

 ~/.config/micro/bindings.json
Ctrl-m": "Quit"

Checked the keybindings document, this one should get supported. But the behavior here, is it would failed to run as expected.

Maybe there's some hard-coded sutff causing this?

Specifications

Commit hash:dd69599f376ce3f0918a2c4d173d708fb67fe0ec
(Both latest master branch, and latest stable version 2.0.10, having this issue)

OS: Debian bullseye
Terminal: Kitty

[zoomosis]

Ctrl-M and Enter both use the same ASCII code: 13. I suspect Micro has Enter internally-wired to perform a carriage return in the editor.

Probably the only way around this (if possible) is to have Kitty remap the literal Ctrl+M keypress to a different code that is then sent to Micro.

[dustdfg]

Still an issue in current master:

Version: 2.0.14-dev.70
Commit hash: 399134f

[dmaluka]

This issue is always gonna be in current master. It is the same issue I wrote about in #2868 (comment)

I think all we can do here is clearly explain in help keybindings that due to limitations of most terminals, micro cannot distinguish between Enter and Ctrl-m, Tab and Ctrl-i, Backspace and Ctrl-h, Tab and Ctrl-Tab, Ctrl-whatever and Ctrl-Shift-whatever...

[dmaluka]

Well...

Terminal: Kitty

and: #2868 (comment)

so: with gdamore/tcell#671 fixed, things might get better (but only with Kitty and a couple of other terminals)...