08:06 <rgallaispou> dnkl: Yup it is closed, which is a bit sad because I was volunteering to help. Anyway, in the issue Chris mentioned a workaround in Vim with something like `:set t_kf3=<c-v><f3>`. I will try this before changing the whole terminal config for just one program. ;)

08:07 <dnkl> rgallaispou: I'm interested in your findings. Might put it up on our wiki.

08:08 <dnkl> fwiw, my suggestion wouldn't change any terminal settings, just vim

08:09 <rgallaispou> Yes, I was thinking about documenting this

08:10 <rgallaispou> Oh okay ! I thought you meant to disable the kitty keyboard protocol for the terminal, but indeed it can be disabled directly in vim

08:36 <dnkl> I wrote a reply. Based on earlier interactions with vim I expect it to be ignored, but hey, you never know

08:41 <dnkl> it looks like you don't have to explicitly disable the kitty protocol in vim, just add the TI/TE workaround to the vim config

08:50 <rgallaispou> dnkl: Thanks for your reply, maybe it will cary more weight

08:51 <rgallaispou> I'll try the workarounds tonight since I don't have the setup right now

10:54 <rgallaispou> "Probably issue needs to be reopen."

11:10 <dnkl> that went better than I expected

11:20 <dnkl> he also mentioned the t_kf3 workaround, but I can't get it to work. But then I'm not a vim-wizard 😅

11:36 <rgallaispou> dnkl: Yeah, I also expected to spend a lot more energy into this

19:25 <rockorager> dnkl: fyi https://github.com/kovidgoyal/kitty/issues/8927

20:17 <ifreund> that would actually be lovely for kakoune