micro not respecting raw escape sequence bindings

I have my terminal setup to send certain escape sequences based on some key combinations. Micro is receiving these escape sequences, but seems to still be binding based on micro key names.

For example, I have Super+Shift+Left setup to send \x1b[1;10D. In my bindings.json, I have:

"\u001b[1;10D": "DuplicateLine",

This is what raw shows when I press that key combination:

EventKey: Shift-Alt-Left: "\x1b[1;10D"

Despite showing the right escape sequence, DuplicateLine does not work. However, if I bind AltShiftLeft to DuplicateLine, it works (note that I'm not actually pressing AltShiftLeft).

To better see what's going on, say I had a bindings.json like this:

  "\u001b[1;10D": "InsertNewline",
  "AltShiftLeft": "DuplicateLine",

Pressing the key combination that sends \x1b[1;10D duplicates the line instead of inserting newline.

So it seems like micro is trying to do some translation from escape sequence to key name which doesn't seem like the correct thing to do. It should just match on the actual escape sequence.

Commit hash: c2cebaa3
OS: macOS
Terminal: wezterm 20230712-072601-f4abf8fd

Start by tracing how bindings.json entries and the raw command's EventKey output are handled at commit c2cebaa3, especially where the escape sequence is translated to a micro key name. Reproduce the macOS/WezTerm example and verify that the literal \u001b[1;10D binding takes precedence over the translated key binding.