4 ms·
I agree that using the 8-bit CSI to eliminate the escape ambiguity would be great. The rest I'm a bit "meh" on. In particular I use C-S as the modifier for my
by aidenn0 6y ago
I agree that using the 8-bit CSI to eliminate the escape ambiguity would be great. The rest I'm a bit "meh" on. In particular I use C-S as the modifier for my terminal shortcuts, so if the terminal could detect it I'd be looking for yet another set of bindings that no terminal programs will ever use.
- alpaca128 6y agoThe only decent solution in my view would be a new, separate kind of terminal spec, maybe even completely focused at terminal emulators. It could make sense to handle input better(maybe even with keyup/keydown events) and maybe display images in a non-hacky way(it can already be done via w3m...kind of). Changing the existing standards just won't work as it would break a ton of programs, although if I'm being honest - while I like the idea of such a terminal rework - I don't know if it can be done nowadays without it opening the flood gates by developers who just can't restrain themselves from adding so many features it might as well be a new browser engine. And either way I don't think it's worth the effort as those input limitations only affect a few specific situations. I use hundreds of custom keybindings in Vim and so far the only obstacle I encountered was the `Tab` & `Ctrl-i` overlap. If I need to hold down more than one modifier I did something wrong anyway.
- aumerle 6y agohttps://sw.kovidgoyal.net/kitty/keyboard-protocol.html https://sw.kovidgoyal.net/kitty/keyboard-protocol.html https://sw.kovidgoyal.net/kitty/graphics-protocol.html https://sw.kovidgoyal.net/kitty/graphics-protocol.html
- alpaca128 6y agoLooks great, the only gripe I have with Kitty is how slow it is, especially on startup. I guess mostly because the combination of Python and tons of features has a negative effect in this area. In fact that was the only reason I switched away from it despite its great font ligature support; I use terminals a lot and so the constant delay when opening a new window was a bit much. However I like those modernised protocols and it would be neat to have widespread support for it.
- aumerle 6y agokitty startup time was slow because of a bug in GLFW, fixed a while ago. And you can have its startup time be 0 with --single-instance.
- bsdubernerd 6y agoIt's still an order of magnitude slower during startup than other terminals such as xterm, rxvt or even mlterm. On my intel laptop I can often see the gl context flashing before becoming the final background color, which is annoying. Requires also way more ram. kitty is a great terminal, but it's one example of fast not being also lightweight.
- aumerle 6y agotime kitty -1 false real 0.098 user 0.080 sys 0.017 maxmem 23 MB faults 0 time xterm false real 0.052 user 0.035 sys 0.000 maxmem 9 MB faults 1 Doesnt look like an order of magnitude to me.
- bsdubernerd 6y agoxterm false 0.06s user 0.01s system 81% cpu 8Mb mem 0.090 total mlterm -e false 0.08s user 0.02s system 84% cpu 13Mb mem 0.125 total kitty -1 false 0.22s user 0.05s system 93% cpu 78Mb mem 0.290 total (and yes, there's a kitty instance running already..)
- aumerle 6y agoI cant reply to your other post, so: you need to run the other kitty instance also with -1. If you do that, you will get the same numbers I got.
- bsdubernerd 6y agoI know, I'm actually using kitty regularly.
- 6y ago