I just tried Alacritty on Linux and think I’ll run with this going forward. I had switched from Konsole to Kitty due to some rendering issues with Yazzi. However, several issues in Kitty:
does not support zoom which I occasionally miss.
Espanso does not work properly – substitutes ‘;’ for ‘:’ which I use extensively in my time tracking system.
Excited to discover Alacritty has zoom (Ctrl +/-), and Espanso works properly. Defaults seem good enough for me. Also seems a bit faster to start.
Because I use Zellij, the features I need in the terminal are minimal. Alacritty seems to fit the bill perfectly.
Now I just need to get zsh going and perhaps I’ll be caught up with @khem
Alacritty has been crashing for me lately – mostly while running Helix inside Zellij, but just crashed while running SIOT tests. This is the workstation still running X, so may be something to do with that. Anyway, back to Kitty for coding for now – nice to have options …
yes, latest Arch here. Tried Wayland again, and only getting 1024x768 resolution on 4K monitors. Not sure what is wrong. Nvidia RTX 3050 card, nvidia-open driver package. Probably need to stay in X anyway for a bit with KiCad as it still relies on wxWidgets.
wxWidget app can run over xwayland without issues I think. I am not suing nouveau driver but the binary driver from Nvidia, latest version works ok with wayland.
There are now 3 options for nvidia: nouveau, nvidia, and nvidia-open. According to Arch wiki, Nvidia recommends nvidia-open for newer cards, but maybe I should try nvidia.
I upgraded to MacOS 15 ( Sequoia ) and alacritty stopped working especially access to local network was disallowed. It was working fine using Terminal.app or Wezterm. It seems it was flagged by OS and quarantined. so do this
I like the idea that no random app can access the network – that makes sense.
However, it is a tradeoff between security and letting you get something done.
I find a stock Linux system is secure enough for me. No magic stuff like Windows and MacOS where it is policing stuff, but the foundations of Linux are solid, which eliminates the need for a lot of this stuff.
ssh_dispatch_run_fatal: Connection to <IP_ADDRESS> port XXXX: message authentication code incorrect
so I tried wezTerm and it worked, now I tried kitty and it works ok too, default OSX terminal app works. So it seems alacritty alone is having this issue.
After running Ghostty for some months, I decided to return to Alacritty. The main reason is startup time. I assign a keyboard shortcut to start my terminal, and Alacritty is nearly instant, whereas Ghostty takes 3-5 seconds. The difference may be because Ghostty uses GTK where Alacritty writes directly to the GPU.
Alacritty also feels slightly faster, but this is subjective.
The following removes the window decoration in Alacritty, which I liked in Ghostty.:
[cbrake@ceres ~]$ more .config/alacritty/alacritty.toml
[window]
decorations = "None"
3-5 seconds is a surprise to me. I have been using Ghostty for 3 months or so on two dev machines and startup is well within a second. My main attraction to Ghostty is the speed with which it can handle several panes of real-time structured debug info (tons and tons of formatting to improve visual impact), and shortcut configuration possibilities. I also love that its written in Zig, and the documentation is the best ever. Clearly I’m a fan