kitty

Those existing tools are poorly designed, if you read the article it has a link to the discussion about its design choices, which contains in turn discussion about all the problems with sixel https://github.com/kovidgoyal/kitty/issues/33#issuecomment-2...

(Author of the original paper here.) Bracketed paste mode is good and ideally it just works(tm) and therefore people don't need to know about it. It does just work in recent versions bash (readline) and Zsh. Unfortunately there is still poor handling of it in some terminals. I posted[1] yesterday on oss-security that ^C for example can be placed on the clipboard and may end bracketed paste mode in some circumstances. For xterm that can be mitigated by adding "ETX" to disallowedPasteControls[2]: disallowedPasteControls: BS,DEL,ENQ,EOT,ETX,ESC,NUL That still isn't enough (e.g. ^\ or ^Z can be used too in some contexts). Other terminals are looking at this currently (e.g. kitty[3]). I suspect there will be some other patches coming out. [1]: https://www.openwall.com/lists/oss-security/2023/10/20/2 [2]: https://www.openwall.com/lists/oss-s

> I tried the first line and in some situations (specifically with some remotes, i.e. kitty -> ssh -> tmux with that 1st line) it still won't fix it. You likely need all of them ;-) IIRC it "fixes" terminfo stuff "within tmux" for kitty regardless of what $TERM is set. Mind you, I was using the latest tmux at that time. tmux 3.2? Here's the issue I had: https://github.com/kovidgoyal/kitty/issues/3018 Looks like it should be fixed on a very recent tmux; otherwise this MIGHT help: set-option -as terminal-features ',xterm-kitty:RGB' ... or not.

Kitty has the wrong width: https://github.com/kovidgoyal/kitty/issues/3810 It doesn't immediately overwrite the emoji with the next character, but the cursor position is off, which leads to wrapping problems down the line.

I don't know of a single terminal that actually gets these ZWJ emoji sequences right. There are several terminals who will render them, but I haven't seen any actually get the width calculations correct. (E.g., https://github.com/kovidgoyal/kitty/issues/3810.) Part of the problem is that it really messes up the idea of a rectangular grid of base characters in memory, so you'll need some sort of indirection. Obviously I haven't tested all terminal emulators in existence, though :-) I patched a similar bug in screen earlier this year (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039503), which indicates the kind of stuff you have to go through.

kitty added support for v3 a couple of years ago: https://github.com/kovidgoyal/kitty/issues/3410

I also know input methods work great on Ubuntu (Gnome Wayland) because Gnome has first-class support for ibus. But the article is specifically about incompatibility of input methods among different DEs: Gnome, KDE, wlroots-based environments such as Sway and Hyprland. After many years, ibus still doesn’t work with wlroots, because ibus supports input method protocol v1 and wlroots supports v2: https://github.com/ibus/ibus/issues/2182 The list of recommended IMEs on Sway are all WIP: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway#... There is even v3. Kitty refused to implement v3 because v3 appeared even more unstable: https://github.com/kovidgoyal/kitty/issues/2814#issuecomment... The wayland input method protocol is stuck at v1, and DEs/applications disagree about which versions to support. That’s why it’s problematic.

Spare a thought for we developers of terminal emulators. The block and line drawing characters have been being bodged since the time that IBM added the extra 9th column in hardware. I have a fairly trivial bodge for them in mine. Kovid Goyal over a period of 7 years has built up an extensive system for overriding the glyphs for block and line drawing characters that are supplied in fonts and replacing them with ones that Kitty constructs itself, all started because they just didn't line up when using what the fonts supplied. * https://github.com/kovidgoyal/kitty/issues/16 * https://github.com/kovidgoyal/kitty/blob/28b84a2d5b2720b88fd...

It's interesting to read the discussion about Sixel support in Kitty [1], where the pros and cons of Sixel are considered in relationship with Kitty. In particular, I find this comment [2] by the maintainer of libsixel particularly intriguing: > After I took over the maintainership of libsixel I unfortunately decided it cannot support the security demands of Kitty, it is too insecure internally. I need to write a Rust library or something. [1] https://github.com/kovidgoyal/kitty/issues/2511 [2] https://github.com/kovidgoyal/kitty/issues/2511#issuecomment...

I believe you can create a TTF font with embedded bitmaps in it. At the specific size, it should use the bitmap font. At other sizes ... , well, don't do that. https://github.com/kovidgoyal/kitty/issues/97#issuecomment-5...

Usually I agree but the maintainer of kitty is bonkers rude. There have been several issues concerning privacy and security regarding kitty. The responses of the maintainer regarding these very valid concerns made me switch to wezterm/sakura/foot in an instant. He also accepts lots of PRs from contributers. Once you do this, it is no longer your project only. An example PR (there are a few others equally concerning): https://github.com/kovidgoyal/kitty/pull/3544

kitty is also worth a look, though it doesn't run on Windows: https://sw.kovidgoyal.net/kitty/ https://github.com/kovidgoyal/kitty/releases I used iTerm2 on macOS for many years and still keep it around, but switched to kitty as my daily driver in late 2021 and have been very happy with it.