the kitty keyboard protocol as implemented by iTerm2 seems to send different codes for F1-F4 keys

[tstack]

iTerm2 seems to send CSI 11~ for F1 instead of SS3 P as shown here. I "fixed" this by adding mappings for CSI 11~ through CSI 14~ for F1-F4 in here:

notcurses/src/lib/in.c

Lines 2103 to 2108 in 3a3c75e

	{ .esc = "\x1bOP", .key = NCKEY_F01, },
	{ .esc = "\x1bOQ", .key = NCKEY_F02, },
	{ .esc = "\x1bOR", .key = NCKEY_F03, },
	{ .esc = "\x1bOS", .key = NCKEY_F04, },
	{ .esc = "\x1b[15~", .key = NCKEY_F05, },
	{ .esc = "\x1b[17~", .key = NCKEY_F06, },

[dankamongmen]

just letitng you know i'm seeing these, ytou're awesome, thanks for filing them, and i will jump up on this as soon as i'm feeling froggy. you're a fucking champion.

[tstack]

just letitng you know i'm seeing these

No worries, I know life exists outside of maintaining open source projects. notcurses has been a huge improvement over ncurses for me, thanks for all your efforts.