![]() Try getting fallback fonts to work properly with urxvt for example, that is what ultimately drove me away urxvt as the rendering issues I encountered with CJK fonts just drove me up the walls. The community is nice and responsive, documentation good, code modern, and configuring it is straightforward (auto reload upon file edit anyone?). Some awesome parts on the side of Alacritty. I also ran into some font scaling issues across monitors, but I suspect urxvt gets around this mostly by being completely ignorant of things that have happened over the last 20 years. However, it is really not something that bothers me during day-to-day usage and I suspect that it will improve over time as urxvt is about as dead as it gets when it comes to a code base. I migrated from urxvt to Alacritty a little less than six months ago, here are some reflections.ĭespite all the talk about performance, I find urxvt to be more responsive. I've had people tell me they cannot do this, so I guess it's a learned skill. It's interesting that a brain is able to recognise particular word-forms that flick by extremely fast, much faster than reading them. I guess in the era when man pages were everything, I got used to scrolling really fast to look for things of interest. I have been known to skim manuals very fast as well. ![]() If I use output filters, then I have to faff about re-running the program with different filters, or with all outputs enabled so I can step through everything around the event of interest.Īdmittedly sometimes its better to output to a file and search the file, but sometimes visual output at 60Hz works quite well. ![]() Either some critical or warning message in a different colour or boldface, or a shape to the messages that I'd recognise.Īlthough in principle I could use various output filters, grep etc., sometimes that's effort and I'd rather just run the thing and have it run quickly.Īlso it's convenient to have all the output readily available if I do want to look at something that happened, as I can scroll to that place and look at pages of surrounding context in detail. > You never watch output that goes by faster than you can read, unless you're actively watching movies through aalib or libcaca.ĭuring development I often run programs that spew an enormous quantity of log output, and I'm watching to see if I notice a pattern in the output visually, or if it just looks normal. Having true-color support is probably the only big argument I can see, which is nice to have for inband images, but again. urxvt always felt more consistent to me, but all three outclass pretty much all other terminals I ever tried.įor those using a tiling window manager, the built-in tabbing and multi-window support is pretty much useless too. It still starts in no less than a full second compared to mere a tenth of a second of urxvt, xterm or mlterm. ![]() Kitty is much better, but it's not exactly a lightweight terminal. It's also hard to measure correctly, because some terminal features such as output reflow and ligature support hide major spikes in latency that you only experience occasionally but can be incredibly annoying (say hi to all url regex matchers!).Īlacritty felt absolutely abysmal in the latency department when I last tried it one year ago, which is even worse than most libvte based terminals. Not to say that optimizing throughput it's useless (total time adds up over the course of a day), but latency and start-up time are really what matters in a terminal emulator. I would be happy to have a "framedrop" equivalent for terminals when this happens, as it's totally useless from my perspective. You never watch output that goes by faster than you can read, unless you're actively watching movies through aalib or libcaca. Displaying gobs of output in a terminal is pretty much the most useless benchmark you can do for a terminal emulator.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |