aumerle

And ctrl+shift+f is the same as ctrl+f for you? The point of using "identical" keybindings is to ease discoverability across programs. ctrl+shift+f and ctrl+f are not identical and therefore there is no point to doing that.

And pretty much anyone that has to deal with internet commenters using the term UX thinks that, not just me.

That shortcut opens HISTORY, hence it is ctrl+shift+H. And if the terminal emulator used up ctrl+f to implement find, it would mean that no terminal program could use ctrl+f to implement find. Maybe next time before you try to imply other people dont know UX, pause, and consider if you know what you are talking about. Incidentally, using the term UX itself, generally is a good signal that the person that is using it doesnt have a clue what they are talking about.

There is an escape code that does clear screen and scrollback invented by xterm \e3J. And kitty invented one that clears screen into scrollback \e22J. https://sw.kovidgoyal.net/kitty/conf/#shortcut-kitty.Reset-t...

To workaround it add the following to your shell's rc file:

function reset { printf '\e]\e\\\ec' }

Uses the VT100 RIS escape code to ask the terminal to reset itself. But first it send an empty OSC escape to reset the terminals VT parser back to normal mode, so that the RIS escape code is parsed correctly. No need to depend on any external utilities like tput or the reset binary. This should work with any halfway decent terminal emulator.

"eventually" is doing a lot of heavy lifting here.

Yes, it does offer a manpage.

Except that kitty's update check defaults to off for distro packaged software and on for non-distro packaged software, without maintainers having to do anything. https://sw.kovidgoyal.net/kitty/conf/#opt-kitty.update_check...

And a full browser runnning in the terminal: https://github.com/chase/awrit

No kitty is not a fork of putty. Thats a different kitty. https://github.com/kovidgoyal/kitty vs https://github.com/cyd01/KiTTY

You need to use --vo-kitty-use-shm=yes when using the kitty backend with mpv.

epubor just uses the calibre derdrm plugin internally, without even acknowledging that, thereby stealing the word of the maintainers of the dedrm plugin.

Umm kitty has native tabs and the developer never tells anyone to tuse tmux, on the contrary he tells people not to use tmux. You are confusing kitty with alacritty.

Or instead it reads like someone thoughtfully came up with a minimal design and then iterated on that based on real world feedback for what is actually useful in this context.

Your only actual complaints were "weird global state" and "no API". I look forward to seeing you design a protocol that involves two way communication between two unrelated entities that avoids some shared state between them. As for no API, this is a protocol specification. if you need an API so badly go browse NPM.

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...

The updates have nothing to do with news parsers. News parsers are loaded dynamically, every time they are used. So are metadata downloading plugins. So are get books stores. Indeed almost all code that parses data from the web in calibre is loaded dynamically independent of calibre updates. The calibre developer whom you so blithely complain about here actually jumps through a million hoops to make sure those bits of calibre remain backward compatible with version of calibre and therefore python, going back a decade and more.

So now any program that's running as your user, even your browser, can edit any file you edit with sudo. It just has to watch for your editor to quit and win a race with sudo to modify the file before sudo reads it.

xrandr is not sufficient for this. One needs a way for users to configure the per monitor DPI. And have the configuration available to X clients. Currently the only cross DE mechanism for this is Xft.dpi and its global, not per monitor.

No, its only slower over PTY because the kitty protocol is transmitting images with higher fidelity, aka color accuracy. So if you want to compare apples to apples get sixel to transmit images with equal fidelity first. I'll go raise three generations of my family while you try to achieve that.

As for infinitely faster, that was obvious hyperbole. For local transmission, using shared memory to transmit RGBA data directly is going to absolutely crush serializing then transmitting over a pipe the de serializing. This is so obvious it doesnt even need to be stated. And the vast majority of image display and indeed terminal usage in general happens locally not remotely. Which is why the kityt protocol sensibly prioritizes that use case.

What nonsense. kitty's graphics protocol is literally infinitely faster than sixels for local transmission and the same speed as sixels for remote transmission, taking into account that kitty's graphics protocol supports 32bit colors, unlike sixel.

neovim supports OSC 52 out of the box so clipboard over SSH should just wrk in kitty or any terminal that supports OSC 52. kitty of course supports a lot more than OSC 52 but for basic opy/paste of plain text, OSC 52 is sufficient.

kitty icat works with tmux, as of kitty 0.28.0 just FYI.

terminal emulators dont actually know this. Just think of executing something via ssh. In this case the primary foreground process is ssh.

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

Heavens! Your terminal opens and reads a file. What a disaster. Still waiting for a concrete issue with the actual kitty graphics protocol. How is it unsafe to feed a terminal that supports the kitty graphics protocol untrusted input. One single solitary example would go a long way to prove you aren't just full of hot air.

FUD as usual. I am so sick of people waving around the security word. If you are scared of dealing with files on Linux, I suggest you throw your computer in the garbage and retire to a mountain fastness with no electricity. If you have a specific criticism of the kitty protocol make it, otherwise spare us the vague FUD.

See https://github.com/chase/awrit for a browser in the terminal

Yup for years. https://github.com/jktr/matplotlib-backend-kitty

Your problem is windows

There's a very vocal group of such people, sadly. Thank you for saying no to them as long as you did. Makes it a little less likely the rest of us will encounter them in our open source projects.

rate limit. Or paywall.