You will never interact with this pipeline if using the Web GPU vulkan renderer, which has its own issues. I personally experience some form of memory leak / latency when working in terminals that have been open for a 'good' amount of time.
[^1]: https://github.com/microsoft/terminal/pull/17510
[^2]: https://devblogs.microsoft.com/commandline/windows-terminal-...
I forked a colorscripts project and added some true ANSI art after conversion and the built in glyphs look so much better than any other font.
It's great but is there any special rendering for the built in glyphs that's not possible with fonts? Just curious
I daily drive a couple Macs and enjoy them but I can't help but notice they seem slower in the terminal than the alternatives. Can't get any kind of discussion on /r/mac as it's just 'Apple silicon is fast!'
I tried the throughput test myself just now between the native macOS terminal and ghostty.
Ghostty: cat /tmp/lines.txt 0.00s user 0.02s system 36% cpu 0.069 total
Native mac terminal: cat /tmp/lines.txt 0.00s user 0.02s system 18% cpu 0.115 total
Seems much faster than any of the OP's windows terminals tested except for MinTTY.
Likewise in one unscientific test with Is It Snappy, ghostty took 8 frames to render the output from pressing the key, but I didn't repeat multiple times.
So, seems faster, but I know what you are talking about, I experience it too. Something about using the terminal on macOS feels sluggish compared to alternatives. It's especially noticeable for me over SSH
CamperBob2•2mo ago
hobs•2mo ago
Otherwise click the top left icon, go to settings, uncheck QuickEdit.
alexchantavy•2mo ago
1718627440•2mo ago
shigawire•2mo ago
Has happened to me quite a few times.
larkost•2mo ago
jwatte•2mo ago
Ctrl-S may or may not end up stopping the program, depending on how much it's printing, and how much output buffering there is before it blocks on writing more.
jwatte•2mo ago