From 3886a2df130820877eeb870bd54c92e4ef281004 Mon Sep 17 00:00:00 2001 From: nick black Date: Sat, 16 Oct 2021 08:19:26 -0400 Subject: [PATCH] README: kitty keyboard protocol --- README.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 771700d53..ebb76a563 100644 --- a/README.md +++ b/README.md @@ -323,10 +323,19 @@ If things break or seem otherwise lackluster, **please** consult the
- Why didn't you just render everything to Sixel? + I'm getting strange and/or duplicate inputs in Kitty. + Notcurses supports Kitty's powerful [keyboard protocol](https://sw.kovidgoyal.net/kitty/keyboard-protocol/), + which includes things like key release events and modifier keypresses by + themselves. This means, among other things, that a program in Kitty will + usually immediately get an `NC_ENTER` `NCTYPE_RELEASE` event, and each + keypress will typically result in at least two inputs. +
+ +
+ Why didn't you just render everything to bitmaps? That's not a TUI; it's a slow and inflexible GUI. Many terminal emulators - don't support Sixel. Sixel doesn't work well with mouse selection. - Sixel has a limited color palette. With that said, both Sixel and the + don't support bitmaps. They doesn't work well with mouse selection. + Sixels have a limited color palette. With that said, both Sixel and the Kitty bitmap protocol are well-supported.