How are Control and Shift combos handled for keymap?

[mwsmws22]

How are control and shift key combos handled in the default keymap?

From the docs it says:

Key presses are converted into a string that is used to lookup an entry in the keymap. Function keys are encoded as an f followed by the key number. Other keys are encoded as UTF-8 bytes and formatted as an x followed by the hex-encoding in lowercase. For example, the encoding for the £ key would be xc2xa3. To make it easier to discover the encoding for unassigned keys, lnav will print in the command prompt the :config command and JSON-Pointer for assigning a command to the key.
Since lnav is a terminal application, it can only receive keypresses that can be represented as characters or escape sequences. For example, it cannot handle the press of a modifier key.

Does this mean we can't assign any custom keymaps for modifier (e.g. shift and control) combos?

For example I see that ctrl + w is word wrap toggle. And from the config I can see that:

"x17": {
    "command": ";UPDATE lnav_top_view SET options = json_set(options, '$.word-wrap', CASE jget(options, '/word-wrap', 'none') WHEN 'none' THEN 'normal' ELSE 'none' END)"
},

So presumably x17 is ctrl+w though I don't know why. I try to use one of those Hex to String converters but get � .

Is x17 actually ctrl+w? Do we have the ability to set modifier combo keymaps?

Many thanks

[tstack]

Does this mean we can't assign any custom keymaps for modifier (e.g. shift and control) combos?

Terminals are somewhat limited in what keys they can receive. The kitty keyboard protocol has improved the situation, but not all terminals implement it. This part of lnav was also written at a time when ncurses was being used and it doesn't support the kitty protocol.

Fast forward to the present and ncurses has been replaced with notcurses in lnav, which does support the kitty protocol. However, I haven't gotten around to updating the config to be able to clearly specify the keys for a hotkey.

So presumably x17 is ctrl+w though I don't know why.

The mapping for control characters is to bitwise-AND the ASCII character value (0x57 for W) with 0x1f.