It kind of seems weird to put unicode in the name but not support astral characters, combining characters or bidi.
I understand these things are complicated for terminals but its weird to so thoroughly emphasize unicode and then not do a significant portion of unicode.
Looks like it's due to fundamental limitations – there's a one-to-one mapping between cells and Unicode code points, and glyphs are blitted from a pre-rendered atlas. (It's very Shadertoy-like.)
I agree it's an awkward situation: ye olde xterm and rxvt can render emoji outside of the BMP, while zutty doesn't seem to be able to.
My terminal emulator has that mapping (because it is designed to be a workalike for kernel terminal emulators that have that mapping). It quite happily supports the other planes. There is no actual fundamental limitation here.
Even with the one-codepoint-per-cell model, what planes one can cover is simply a matter of whether an integer is 16-bit or 24-bit/32-bit. In the Zutty code, it's a 16-bit integer, and I suspect that that is a knock-on effect of the particular way that it flattens fonts out and maps code points to glyph bitmaps, which isn't the only way that one could do that.
In short: it's a terminal emulator where rendering is completely run by GL ES compute shaders. It allows for GPU-accelerated performance on low-end SBCs.
Said to be very stable, runs for months, compliant enough to run Emacs with mouse support.
It probably will not catch on, I suspect. Wiktionary lacks the word completely, it appears, not even its Hungarian flavour having it, giving an indication of how obscure it is going to be when non-native speakers try to look it up.
I’ve used this but it made my laptop spontaneously reboot a few times (or was it a hard lockup that necessitated a reboot)? I liked it but ended up putting it away.
Dual GPU nvidia and integrated Intel, was running the latest Ubuntu LTS at the time with all updates.
And that's why it is best to avoid GPU-acceleration unless you truly need it.
GPU drivers have always been full of bugs and will always be, since modern GPUs are ridiculously complex and designed for speed rather than reliability.
My workday is 95% terminal, I work on a company managed windows 11 machine using git-scm as an easily updateable min-gw environment. A git-bash has been my configurable linux terminal on windows.
Why would one need a gpu accelerated terminal? What's the use case here?
I mean, I've worked on connections offering a an mbit of throughput. That was enough for the kind of work I'm doing.
I really do not understand what this is for, can someone enlighten me please?
Well, in the age of 3440x1440 displays and retina, you are forced to render high-quality fonts, not just bitmaps. In order to do that well, and fast enough, you need the GPU.
I see. I'm still holding on to my 3:4 aspect ratio EIZOs as second screen just because I prefer having a smaller second screen instead of 2 huge widescreens.
Opting into anything higher than 1920x1080 seems uncomfortable for me.
Maybe I just get old. I find it hard to read fonts on higher resolutions and it seems like other people do as well..
16pt Lucida Console on 1920x1080 just works way too well for me to even consider switching to anything else.
As I got older, I've noticed I was slouching more and more. So I got one of those LG UltraGear 45” curved monitors. It's gigantic, but helped me so much with posture and eye strain. I view every website at 200% or 250% zoom, my text editor has Inconsolata at 28px.
Of course, that came with some pains. Managing windows was time consuming, so i3 came into the picture. rxvt and st got slow, so zutty came to the rescue.
But I would be a liar if I didn't say that I miss 1024x768 with pixel-perfect fonts and UI widgets.
It kind of seems weird to put unicode in the name but not support astral characters, combining characters or bidi.
I understand these things are complicated for terminals but its weird to so thoroughly emphasize unicode and then not do a significant portion of unicode.
Looks like it's due to fundamental limitations – there's a one-to-one mapping between cells and Unicode code points, and glyphs are blitted from a pre-rendered atlas. (It's very Shadertoy-like.)
I agree it's an awkward situation: ye olde xterm and rxvt can render emoji outside of the BMP, while zutty doesn't seem to be able to.
The documentation is a pleasure to read, though.
My terminal emulator has that mapping (because it is designed to be a workalike for kernel terminal emulators that have that mapping). It quite happily supports the other planes. There is no actual fundamental limitation here.
Even with the one-codepoint-per-cell model, what planes one can cover is simply a matter of whether an integer is 16-bit or 24-bit/32-bit. In the Zutty code, it's a 16-bit integer, and I suspect that that is a knock-on effect of the particular way that it flattens fonts out and maps code points to glyph bitmaps, which isn't the only way that one could do that.
In short: it's a terminal emulator where rendering is completely run by GL ES compute shaders. It allows for GPU-accelerated performance on low-end SBCs.
Said to be very stable, runs for months, compliant enough to run Emacs with mouse support.
The source code is locked behind a login though. Is that intentional?
Edit: just the web view is locked. Read the homepage, it tells you how to access the code (be respectful though, don't hug the site to death)
Homepage: https://tomscii.sig7.se/zutty/
This is also great: https://tomscii.sig7.se/2021/01/Typing-latency-of-Zutty
The typing latency on zutty is the biggest feature for me. Everything feels snappy.
https://tomscii.sig7.se/2020/12/A-totally-biased-comparison-... is also useful as a comparison piece.
I can pronounce the name of this software correctly. Now that's something I guess.
https://tomscii.sig7.se/zutty/wiki/FAQ.html#How%20do%20I%20c...
It probably will not catch on, I suspect. Wiktionary lacks the word completely, it appears, not even its Hungarian flavour having it, giving an indication of how obscure it is going to be when non-native speakers try to look it up.
* https://hu.wiktionary.org/wiki/zutty
* https://en.wiktionary.org/wiki/Appendix:Hungarian_words_Z
Francophones are going to be thinking of something else. (-:
* https://fr.wiktionary.org/wiki/zut
sadly, not an ASR33 teletype emulator. I miss my teletype, it got broken in an office move. chonka-chonka-chonka-chonka-chonka-chonka----chonka TING
I’ve used this but it made my laptop spontaneously reboot a few times (or was it a hard lockup that necessitated a reboot)? I liked it but ended up putting it away.
Dual GPU nvidia and integrated Intel, was running the latest Ubuntu LTS at the time with all updates.
And that's why it is best to avoid GPU-acceleration unless you truly need it.
GPU drivers have always been full of bugs and will always be, since modern GPUs are ridiculously complex and designed for speed rather than reliability.
eek what? That shouldn't happen on a modern OS, unless the cpu spiked so hot the computer decided the best course is a reboot.
Typically it's a RAM issue, or power stability issue or a graphics card issue/firmware causing instant reboots
Unfortunately, it often does. I've run into this on both AMD and NVIDIA hardware.
> That shouldn't happen on a modern OS
They're running Ubuntu.
Care to explain? Sorry I don't use ubuntu but the claim that the OS just straight up reboots during normal operations is particularly concerning.
My workday is 95% terminal, I work on a company managed windows 11 machine using git-scm as an easily updateable min-gw environment. A git-bash has been my configurable linux terminal on windows.
Why would one need a gpu accelerated terminal? What's the use case here?
I mean, I've worked on connections offering a an mbit of throughput. That was enough for the kind of work I'm doing.
I really do not understand what this is for, can someone enlighten me please?
Well, in the age of 3440x1440 displays and retina, you are forced to render high-quality fonts, not just bitmaps. In order to do that well, and fast enough, you need the GPU.
Font rendering is hard:
https://faultlore.com/blah/text-hates-you/
https://pandasauce.org/post/linux-fonts/
https://behdad.org/text2024/
So much that Slug is a thing:
https://sluglibrary.com/
I see. I'm still holding on to my 3:4 aspect ratio EIZOs as second screen just because I prefer having a smaller second screen instead of 2 huge widescreens.
Opting into anything higher than 1920x1080 seems uncomfortable for me.
Maybe I just get old. I find it hard to read fonts on higher resolutions and it seems like other people do as well..
16pt Lucida Console on 1920x1080 just works way too well for me to even consider switching to anything else.
As I got older, I've noticed I was slouching more and more. So I got one of those LG UltraGear 45” curved monitors. It's gigantic, but helped me so much with posture and eye strain. I view every website at 200% or 250% zoom, my text editor has Inconsolata at 28px.
Of course, that came with some pains. Managing windows was time consuming, so i3 came into the picture. rxvt and st got slow, so zutty came to the rescue.
But I would be a liar if I didn't say that I miss 1024x768 with pixel-perfect fonts and UI widgets.