Sadly Kitty is very bare-bones. Not really for me. And I can't choose to use Kitty in VSCode.
Care to elaborate? I had an impression that it's a pretty complete piece of software. I've been driving it daily for more than 1½ years, and I'm pretty happy with it.
I didn't even realize, I don't see a need for it anyway.
> Ctrl-F to find, did not exist
That's because Kitty has something much better:
> Sometimes you need to explore the scrollback buffer in more detail, maybe search for some text or refer to it side-by-side while typing in a follow-up command. kitty allows you to do this by pressing the ctrl+shift+h shortcut, which will open the scrollback buffer in your favorite pager program (which is less by default).
> There's no menu bar at all in fact.
Which is a big plus. Emacs has a menu bar (and a toolbar), and I obviously turn them off, because they take up screen real estate.
Ah yes, the logical shortcut for "find" (enormous face palm).
Why do so many open source devs find sane UX so hard? It's a bit weird.
(And yes I know it isn't exactly the same as "find" - it that is your instinctive response then you're misunderstanding how UX works.)
Gnome Terminal sensible uses Ctrl+Shift+F to get around this. Kitty... does not.
> 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.
Of course you think that.
And pretty much anyone that has to deal with internet commenters using the term UX thinks that, not just me.
I said most terminal emulators are cross platform and that hot key isn't an OS dependant thing. You then reply with:
> On Mac you can press Ctrl-K in any terminal emulator ... > On Linux no terminal emulators support this
which not only contradicts what I said, it also misunderstands how terminal emulators work
> and I can't choose to use Kitty in VSCode.
So the issue is VSCode doesn't support ctrl+k? that's very different to the statement you opened with