Hi all,
Over at ki-editor/ki-editor, we're looking to make use of the Kitty Keyboard Protocol. Supporting Windows is important to us, and to this point we've been making use of crossterm.
However, PushKeyboardEnhancementFlags can never be run on windows, no matter what terminal is in use. Despite the fact that Alacritty (or Kitty, etc) support KKP, the Command unconditionally fails on windows, because in windows, if the windows terminal doesn't support the ANSI code, we use winapi to execute the command, but the winapi call for KKP unconditionally fails.
One solution to this is a feature flag that forces ANSI even on Windows. We aim to pretty much hard require KKP, so this is more or less acceptable to us. However, this is pretty much directly opposed to crossterm's goals and is a decent chunk of complexity.
Activity
2
Riolku9mo ago...though come to think of it, we could manually write the ansi codes for the KKP commands? But that seems a bit hacky, I guess.
TL;DR, we want to get KKP to work in Alacritty/Kitty on windows, ideally using crossterm, but if there's no good solution, we may simply use some other terminal backend