I'm probably late to the party, but would like to report that helix on alacritty works perfectly. If the default font is missing a character, alacritty appears to be able to find it in another font in the font path.
I'm using this setup for 2-3 years on OpenBSD and previously Alpine without any issues. > On 26. Oct 2026, at 3:06 AM, Dave Polaschek <[email protected]> > wrote: > > I’ve got a machine running OpenBSD 8.0 with all the patches (as of a few > minutes ago). > > I’ve set LC_CTYPE to en_US.UTF-8. printenv shows that it’s set. > > My terminal type when I ssh in is xterm-256color. > > The terminal I’m using on my Chromebook is hterm (https://hterm.org/x/ssh/faq > ) which supports UTF-8, and I’m using Google’s “Noto Sans Mono” as my > terminal font, which has the characters I’m testing. > > If I type a ¢ into it, for example, I get the hex-escapes displayed in > /usr/bin/vi, but when I save the file and dump it using more or cat, the ¢ > comes out correctly. > > Is there some setting I need to tweak to get vi to display UTF-8 characters > correctly, or am I just running into a limitation of vi here? I don’t need > anything more than ASCII most of the time, but it would be nice to be able to > make sure I’ve typed the correct unichar without having to ^z out and cat the > file to be sure. > > Thanks! > > -DaveP
