From: voidscuttle <voidscuttle@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Wezterm ask for Jetbrains Mono Font
Date: Thu, 24 Nov 2022 20:35:58 +0100 [thread overview]
Message-ID: <20221124193558.eyoRtHpgDl7f6mCWHI3eaT4U3QI548XDyjRJ9ydQGV4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40736@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
New comment by voidscuttle on void-packages repository
https://github.com/void-linux/void-packages/issues/40736#issuecomment-1326795244
Comment:
I'm experiencing something similar but a bit different.
1. Launching wezterm without a wezterm config file does not work and produces this:
```
ERROR mux::connui > Configuration Error: Unable to load a font specified by your font=wezterm.font('JetBrains Mono', {weight="Regular", stretch='Normal', style=Normal}) configuration. Fallback(s) are being used instead, and the terminal may not render as intended. See https://wezfurlong.org/wezterm/config/fonts.html for more information
ERROR wezterm_gui::frontend > Failed to create window: failed to get font metrics!?: obtaining metrics for font_size=12 @ dpi 96: unable to load font idx 1!?
```
2. Launching wezterm with a config file with a different font (e.g. Iosevka) specified launches the terminal as expected and runs normal commands. However when attempting to run a command prefixed with doas (I would assume sudo is the same but I do not have it installed to test) results in the command hanging and a second wezterm window spawns with this error repeated over and over:
```
Unable to load a font matching one of your font_rules: wezterm.font('JetBrains
Mono', {weight="Regular", stretch='Normal', style=Normal}). Fallback(s) are
being used instead, and the terminal may not render as intended. See https://
wezfurlong.org/wezterm/config/fonts.html for more information
```
next prev parent reply other threads:[~2022-11-24 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 17:01 [ISSUE] " AgarimOSLinux
2022-11-24 17:27 ` classabbyamp
2022-11-24 19:35 ` voidscuttle [this message]
2022-11-24 19:53 ` jbenden
2022-11-24 21:02 ` jbenden
2022-11-25 5:18 ` [ISSUE] [CLOSED] " classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221124193558.eyoRtHpgDl7f6mCWHI3eaT4U3QI548XDyjRJ9ydQGV4@z \
--to=voidscuttle@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).