Some emojis haunt ghostty with unspeakable curses

[ixxie]

Certain emojis seem to render a sequence of weird glyphs on the screen that almost look understandable are pretty much illegible.

From testing:

• Seems to influence mulitiple editors and shells
• Triggered by some emojis (e.g. 💤) but not others (e.g. 🍽️)
• Happens in Ghostty but not Alacritty

I'm on NixOS with Home Manager, and you can find my full system configuration here, in particular shell and terminal config and font configuration here and here.

The font is MonaspiceKr Nerd Font, a Nerd Fonts patched version of GitHub's Monaspace Krypton. Didn't have time to try to test other fonts.

The emoji in the following screenshots is 💤:

Nano:

Neovim:

Helix:

Bash:

Fish:

Nushell:

While these are certainly the most enchanting glitches I have ever seen, they are distracting, and have summoned Chuthulu to my office on more than one occassion.

[rhodes-b]

I can run echo "💤" perfectly fine in ghostty using the default font did you try that?

[ixxie]

When I disable all my special font configuration, the error goes away; this is probably just due to disabling the emoji font, since removing only the emoji font also prevents the issue. However, without that configuration, all emojis are invisible.

[qwerasd205]

To help narrow this down can you use ghostty +show-face --string="💤" to figure out what font Ghostty thinks the glyph should be from? And as a bonus, also do it with --presentation=text and --presentation=emoji

[ixxie]

Oddly, the issue doesn't anymore reproduce with this particular emoji, but the emoji is invisible in all these commands:

It did remind me however that I configured Noto Emoji as my emoji font.

[ixxie]

With 📦:

[ixxie]

After updating my system's build inputs and rebuilding it, the weird characters completely disappeared.

However, emojis are not rendering at all.

[mitchellh]

This looks like it's rendering the full (or a lot of) the font atlas. I would imagine that's due to one of:

1. A font metrics issue (in the font itself)

2. A math issue (in our font subsystem)

In either case, what we would need to reproduce this would be a font file (ttf/otf) and a sequence of codepoints that causes this to happen.

[ixxie]

It may be related to NixOS/nixpkgs#327846