No fonts contain glyphs for these codepoints: \u{1f6d1}. Placeholder glyphs are being displayed instead. You may wish to install additional fonts, or adjust your configuration so that it can find them. Set warn_about_missing_glyphs=false to suppress this message.

[hrqmonteiro]

What Operating System(s) are you seeing this problem on?

Linux Wayland

Which Wayland compositor or X11 Window manager(s) are you using?

KDE Plasma (Kwin)

WezTerm version

wezterm 20230712-072601-f4abf8fd

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

No fonts contain glyphs for these codepoints: \u{1f6d1}.
Placeholder glyphs are being displayed instead.
You may wish to install additional fonts, or adjust
your configuration so that it can find them.
Set warn_about_missing_glyphs=false to suppress this
message. 

To Reproduce

Just open it

Configuration

local wezterm = require "wezterm"

return {
  color_scheme = "nord",
  enable_tab_bar = false,
  font = wezterm.font("FiraCode Nerd Font"),
  font_size = 12,
}

Expected Behavior

To not show it

Logs

No response

Anything else?

No response

[aShabat]

Download Noto Emoji font. It contains required glyph.

[Luladjiev]

Any updates on this? I've tried installing Noto Emoji font, but still the same error appears and the glyph is missing, using Windows 11.

[hrqmonteiro]

Download Noto Emoji font. It contains required glyph.

Still doesn't work.

[othman316]

I'm having the same issue, using nerd fonts and I already have noto-fonts-emoji

[hopezh]

I'm having the same issue, with codepoints: \u{f63d}.

System info: Wezterm: 20240203-110809-5046fc22 Windows 11

[radutomy]

Same problem Is there a way to tell what component is causing this warning message?

[benjamin-leopold-tfs]

I get same error, but for \u(1f784, a "Black Slightly Small Circle". Instead of setting the warn_about_missing_glyphs=false, I prefer to have all the glyphs. The builtin fonts are not finding them, though...?

Using the test command from the Troubleshooting Fonts section, it shows that character is coming from Jet Brains Mono...

─▶ wezterm ls-fonts --text a🞄b
13:31:01.727  WARN   wezterm_font > No fonts contain glyphs for these codepoints: \u{1f784}.
Placeholder glyphs are being displayed instead.
You may wish to install additional fonts, or adjust your configuration so that it can find them.
https://wezfurlong.org/wezterm/config/fonts.html has more information about configuring fonts.
Set warn_about_missing_glyphs=false to suppress this message.
LeftToRight
 0 a    \u{61}       x_adv=10 cells=1  glyph=a,189  wezterm.font("JetBrains Mono", {weight="Regular", stretch="Normal", style="Normal"})
                                      <built-in>, BuiltIn
 1 🞄    \u{1f784}    x_adv=10 cells=1  glyph=.notdef,0    wezterm.font("JetBrains Mono", {weight="Regular", stretch="Normal", style="Normal"})
                                      <built-in>, BuiltIn
 5 b    \u{62}       x_adv=10 cells=1  glyph=b,214  wezterm.font("JetBrains Mono", {weight="Regular", stretch="Normal", style="Normal"})
                                      <built-in>, BuiltIn

So now I'd like to know which font does have that one. If the Noto google font has it, then I can set that one up - as a fallback or as a "family" in some certain type??

Thanks for your help!!

[richardguinness]

I resolved a similar issue with \u{e6b4} by installing a Nerd font (e.g. https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts/JetBrainsMono) which includes additional glyphs. Then edited my wezterm.lua with config.font = wezterm.font("JetBrainsMono NF").

wezterm ls-fonts --text x (pasting the symbol represented by unicode ue6b4 in place of "x") now indicates that Wezterm finds that glyph successfully, whereas previously it indicated it couldn't find it. Installing Noto Emoji and Noto Color Emoji (the latter is included in Wezterm I think) and setting these as a fallback in wezterm.lua didn't help.

[lubosmato]

I had same issue on Windows platform.

• Font: FiraCode Nerd Font
• Glyph: \ue6b4 (prettier icon)
• wezterm 20240203-110809-5046fc22
• Windows Terminal shows glyph correctly (ruling out missing glyph in the font)

(wezterm 20240203-110809-5046fc22)

However I also tried nightly version of WezTerm and this particular glyph is correctly displayed there.

(wezterm 20250210-212000-f8921727)

It seems like this problem was addressed and is fixed.

[mayorbyrne]

I had same issue on Windows platform.

• Font: FiraCode Nerd Font
• Glyph: \ue6b4 (prettier icon)
• wezterm 20240203-110809-5046fc22
• Windows Terminal shows glyph correctly (ruling out missing glyph in the font) However I also tried nightly version of WezTerm and this particular glyph is correctly displayed there. It seems like this problem was addressed and is fixed.

Same issue, resolved with the nightly build. Any plans to get this in a stable version?