kitty keyboard protocol not disabled after running notcurses-demo in iTerm2

[tstack]

Hi there,

After running notcurses-demo in iTerm2 on MacOS 15.1.1, keyboard input is all messed up. Pressing keys just spits out escape codes like the following:

u3;1:3uu;1:3u7442;5u9;5u9;5:3u7442;1:3u7442;5u9;5u9;5:3u9;5u9;5:3u9;5u9;5:3u7442;1:3u3u3;1:3u3u3;1:3u3u3
;1:3u3u3;1:3u:3uu;1:3uu;1:3u3u3;1:3u3u3;1:3u7u7;1:3u

I'm guessing the kitty keyboard protocol is enabled, but not disabled before exit?

Thanks

Please include the following data:

• export | egrep 'LANG|LC_CTYPE|TERM'

COLORTERM=truecolor
ITERM_PROFILE=Default
ITERM_SESSION_ID=w0t0p0:68157217-8854-437A-9458-1D089E6551C6
LANG=en_US.UTF-8
LC_TERMINAL=iTerm2
LC_TERMINAL_VERSION=3.5.10
TERM=xterm-256color
TERMINFO_DIRS=/Applications/iTerm.app/Contents/Resources/terminfo:/usr/share/terminfo
TERM_FEATURES=T3CwLrMSc7UUw9Ts3BFGsSyHNoSxF
TERM_PROGRAM=iTerm.app
TERM_PROGRAM_VERSION=3.5.10
TERM_SESSION_ID=w0t0p0:68157217-8854-437A-9458-1D089E6551C6

• notcurses version (available from notcurses-demo i)

• terminal name + version

iTerm2 Build 3.5.10

[tstack]

I've "fixed" this by sending \x1b[=0u to turn off the enhancements before sending the pop (\x1b[<u). That seems to make things work again.

[dankamongmen]

time to dig out the osx laptop and bring it up to date with the world!

[mdiiorio]

Not sure if this was implied by your fix, but it took me a minute to figure out. In case anyone else runs across this I was able to fix on an unpatched notcurses by doing:

    puts("\x1b[=0u");
    notcurses_stop(nc);