💾 Archived View for capsule.jbowdre.lol › gemlog › 2024-04-19-trying-tabby-terminal.gmi captured on 2024-05-26 at 14:36:02. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-05-10)
-=-=-=-=-=-=-
A recent toot from Jack Baty[1] introduced me to the lovely Berkeley Mono font[2]. One thing led to another and, well, I purchased the first font I've ever paid for (seriously, it's *that good*).
Installing the font for use in VS Code didn't take too much effort; I just dropped the relevant TTF files into `/usr/fonts/share/truetype/`and then updated my VS Code config[1].
Being able to use the new font in my terminal emulator posed a more difficult problem. You see, my primary computer is a Framework Chromebook, where I do most of my work in the "Crostini" Linux development environment[1]. So I'm essentially using a Debian container inside of a hardened VM inside of ChromeOS, and there's some special plumbing to make it feel like a more native experience. It works brilliantly for my needs, but does sometimes introduce some interesting hurdles.
1: "Crostini" Linux development environment
Like not being able to select a user-installed font in the default Terminal application (which runs as a ChromeOS web app and gets magically piped through to the container).
I decided maybe it was time to look at a different terminal emulator, and a short survey of available options led me to Tabby[1]. It's nice to look at, quick to run, packed with features and options, and (of course) makes it easy to adjust the theme with my preferred colors and fonts. As an added bonus, it's available across platforms so I can have the same terminal experience on my Linux-focused Chromebook and on my Windows systems as well. Neat!
So far, I'm really impressed with Tabby and will likely be using it at least until Mitchell Hashimoto is ready to share the Ghostty terminal emulator[1] he's been tinkering with.
📡 Originally posted on Scribbles
─────
CC BY-SA