The CLI offers 50+ Themes to choose from, an option to create your alacritty.yml config file with a simple, easy and intuitive user experience. To find the list of themes, you can visit the alacritty wiki page That's why I have created alacritty-themes for that. But when it comes to customizing colors it definitely needs an intuitive tool for the job.
You can config your alacritty terminal by having a config file called alacritty.yml in your home folder like ~/.config/alacritty/alacritty.ymlĬonfiguring your terminal with yml files is definitely fun. It supports scrollback, 24-bit colors ( w:Color depthTrue color (24-bit), copy/paste, clicking on URLs, and custom key bindings. I have been using it for a while now and I really love it. Alacritty is a simple, GPU-accelerated terminal emulator written in Rust. It is incredibly fast and responsive to the extent that I have replaced iterm2 with alacritty for my Macbook, my Ubuntu Laptop and my RasberryPi ArchLinux system. It currently supports macOS, Linux, BSD, and Windows. Using the GPU for rendering enables optimizations that simply aren't possible without it. In this post we are going to take a look at a new CLI tool I have created for customizing colors for your alacritty terminal.Īlacritty is a cross-platform, GPU-accelerated terminal emulator written in Rust. Then a fork that introduces a bunch of bugs, but works.Īnd then a fork of that fork (this is the one in question, zenixls2's) which resolves those bugs and as far as I can tell from their testing ( ) doesn't introduce performance issues. Then there's the middle chunk which focuses on "well, if you won't do it, and I can't code, lets fund the effort so someone else can" which doesn't seem to get anywhere.įinally, a pull request that is again pushed aside for 'performance issues'. As far as I can tell the first bit of the thread consists of "How should we implement? Here are examples from Kitty, iTerm, etc", then the conclusion that the required changes for ligatures (which incidentally also allow CJK and bidirectional text) are too expensive in terms of 'performance'. I've done that before, just did so again now. There are a number of issues described with the various forks implementing ligatures. Please take the time to read through this very thread. Alacritty is the first terminal which feels as fast and snappy as GLterm back in the day 😉 Vim, then ligatures “appear”.)Įdit: BTW, Alacritty is awesome! It reminds me of GLterm, which was my go-to terminal emulator back in the early 2000s (mentioned here, the official site at seems dead). Of course, if the same line used for input receives output from a program e.g. I suppose that it's easier to handle because it's not needed to backtrack and redraw the line where the cursor is to have ligatures applied during input:
#Alacritty windows code#
One terminal emulator that handles them quite well in my experience is Pangoterm, though I have not looked at the code to see whether it does something explicitly or it just delegates the task to Pango - anyway, leaving the link here as reference, in case it's useful to gather inspiration from its code.įor reference, the following screenshot shows an interesting behaviour of Pangoterm: ligatures are not handled in the lines/cells where used input is done, but only in the ones where output is shows.
Support for ligatures would be indeed super nice.
0 kommentar(er)
