181–190 of 323 posts
I like KiTTY on Windows. If you want it to be more visually appealing than PuTTY, I found this repository helpful: https://github.com/yograf/kitty-solarized Clone it/download the .zip and replace the kitty.exe with a recent one
Earlier quoted context omitted.
You may have better font rendering (anti-aliasing support on low-dpi screens), faster rendering and scrolling, better support for terminal attributes (crossed-out, overline, italic, etc). iTerm does a lot of optimizations so it can render and scroll faster (I volunteered to add a feature to it, and I dug a bit through the code). For instance, iTerm supports italic, which Terminal.app doesn't. Gnome's terminal (vte, a…
For instance, iTerm supports italic, which Terminal.app doesn't It does (just checked).
Tried it out and it seems ok. It does seem quite responsive and wasn't too hard to customize. Doesn't have a lot of discoverability out of the box since there's no menus: I had to search through the config file to figure out that tabs exist and that to make one I need to enable the command. I would love a guide of some sort: perhaps a video showing some of the features and how they would fit into a workflow. I toyed…
And now I feel old. Menus in a terminal? Videos explaining a terminal emulator ? Migration guide from arbitrary terminal emulators configs? Get off my lawn! Kids these days, never having had to compile their own xterm and then seeing the light of our holy lord and saviour rxvt, and its endless man pages. There's a huge configuration doc[1], and the homepage already does a very good job of introducing you to its featu…
More importantly, making a video probably takes more time that having a nice write-up about anything.
I am 26, BTW.
Earlier quoted context omitted.
Can we not start throwing around these bullshit `time blah` tests. They don't measure what people thing they measure. It doesn't measure rendering speed at all. It does vaguely measure two things: 1) How big the buffer is on the terminal when it reads in lots of output. If the buffer is as big as the output then your test reports a figure close to the `/dev/null` test. Not useful. 2) How well the terminal is in SKIPP…
Please suggest better methods then.
Earlier quoted context omitted.
Iterm2 also supports GPU accel. FYI
Only in beta, or did they release it?
I tried it on MacOS (MBP retina) and damn, it renders text awfully.
Two simple speed tests: time find ~ /dev/null takes 8 seconds alacritty takes 8.5 seconds and uses 75% CPU kitty takes 15 seconds and uses 100% CPU konsole takes 16 seconds and uses 100% CPU time for i in {1..2000000}; do echo $i; done /dev/null takes 8 seconds alacritty takes 16 seconds and uses 75% CPU kitty takes 17 seconds and uses 100% CPU konsole takes 16 seconds and uses 98% CPU
How long between key press and character render? That's all I care about. 24 cores and still have lag when I type. My 7mhz Amiga 500 had a more fluid GUI than modern PCs. It's disgusting.
Earlier quoted context omitted.
Input latency makes for a bad user experience. People just usually don't notice it when typing as it's so common. See https://danluu.com/term-latency/ for measurements of some terminal software and discussion of why latency is bad. I'm not sure if Kitty is using GPU specifically to minimize latency, but it would be a good reason.
I work in video and as a consequence I tend to be very sensitive to latency (I've spent more hours than I can count trying to figure out subtle synchronization issues) yet I've just spent one minute trying to detect input latency on my st terminal (which fares pretty badly in the benchmark you linked) without success. And that's running inside tmux on top of that. That being said I think it is valuable to have a reas…
Earlier quoted context omitted.
Please suggest better methods then.
Assuming the terminal programs don't 'announce' when they've finished rendering, the only way to this test properly would be a white-box approach, hooking into the code of the various terminal programs, right?