From: Tobias Geerinckx-Rice <me@tobias.gr>
To: jgart <jgart@dismail.de>, guix-devel@gnu.org
Subject: Re: What's missing from qutebrowser for text rendering?
Date: Mon, 02 Jan 2023 17:48:05 +0000 [thread overview]
Message-ID: <98618046-4965-4429-BBDE-1F711B77FBDC@tobias.gr> (raw)
In-Reply-To: <717f94557d09d046e12ad56e33889610@dismail.de>
Thanks. Could you try adding a few mainstays, such as Bitstream Vera & DejaVu, and make sure that fc-cache -rv returns no errors? (Some being ENOENT is fine).
That usually placates IceCat, at least.
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2023-01-02 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 17:34 What's missing from qutebrowser for text rendering? jgart
2023-01-02 17:35 ` Tobias Geerinckx-Rice
2023-01-02 17:39 ` jgart
2023-01-02 17:48 ` Tobias Geerinckx-Rice [this message]
2023-01-02 18:08 ` jgart
2023-01-03 3:45 ` Zhu Zihao
2023-01-04 0:55 ` jgart
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=98618046-4965-4429-BBDE-1F711B77FBDC@tobias.gr \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).