From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Wezterm ask for Jetbrains Mono Font
Date: Fri, 25 Nov 2022 06:18:30 +0100 [thread overview]
Message-ID: <20221125051830.hNcTJ_qnMYSqBOiern2bYv87E3QsUxoyZ34bok7i7cM@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: 1133 bytes --]
Closed issue by AgarimOSLinux on void-packages repository
https://github.com/void-linux/void-packages/issues/40736
Description:
### Is this a new report?
Yes
### System Info
Void x86_64
### Package(s) Affected
wezterm-20221119_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
It should work fine without JetbrainsMono font.
### Actual behaviour
Wezterm complaint about JetbrainsMono font. Its almos impossible to use the terminal emulator without installing this font.
Once installed the font it works as usual.
There were another font that i guess i had it installed in my system.
My opinion: rebuild it without any font dependency and with fonts.patch (no font included in package). Everybody has several fonts in their machines.
Also you could use again the font.patch again like in the former version.
Otherwise you could create new packages from the missing fonts. I don't think is a good idea.
### Steps to reproduce
1) Start wezterm
2) Execute a command (like update the system).
3) New windows with error opens.
prev parent reply other threads:[~2022-11-25 5:18 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
2022-11-24 19:53 ` jbenden
2022-11-24 21:02 ` jbenden
2022-11-25 5:18 ` classabbyamp [this message]
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=20221125051830.hNcTJ_qnMYSqBOiern2bYv87E3QsUxoyZ34bok7i7cM@z \
--to=classabbyamp@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).