From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: IceCat from Guix all monospaced font
Date: Sat, 4 May 2019 19:45:33 +0200 [thread overview]
Message-ID: <20190504174533.zx6qi5y67zlgidld@pelzflorian.localdomain> (raw)
In-Reply-To: <ba2f2e88-5f04-7d0f-3ca9-02d872bc882b@gmail.com>
On Sat, May 04, 2019 at 07:19:40PM +0200, Zelphir Kaltstahl wrote:
> My guess is, that somehow Icecat installed via Guix is not able to pick
> up system wide installed fonts and always, no matter what I set, falls
> back to a monospaced font. Following this guess, I installed Liberation
> fonts and DejaVu fonts in Guix. However, still everything is monospaced.
>
> Also note, that I created a completely new user profile for Icecat, in a
> non-default path in `~/user/.icecat/profiles`. So everything there
> should be clean. That directory did not even exist, when I created the
> profile.
>
The manual says:
After installing fonts you may have to refresh the font cache to use
them in applications. The same applies when applications installed via
Guix do not seem to find fonts. To force rebuilding of the font cache
run ‘fc-cache -f’. The ‘fc-cache’ command is provided by the
‘fontconfig’ package.
If I remember correctly, this helped me when I had encountered this issue.
next prev parent reply other threads:[~2019-05-04 17:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 17:19 IceCat from Guix all monospaced font Zelphir Kaltstahl
2019-05-04 17:45 ` pelzflorian (Florian Pelz) [this message]
2019-05-04 18:19 ` Zelphir Kaltstahl
2019-05-04 20:26 ` pelzflorian (Florian Pelz)
2019-05-05 0:50 ` Zelphir Kaltstahl
2019-05-05 5:55 ` pelzflorian (Florian Pelz)
2019-05-05 12:09 ` Zelphir Kaltstahl
2019-05-04 17:51 ` Tanguy Le Carrour
2019-05-04 18:20 ` Zelphir Kaltstahl
2019-05-04 19:25 ` ison
2019-05-04 20:00 ` Zelphir Kaltstahl
2019-05-04 20:01 ` Zelphir Kaltstahl
2019-05-04 20:14 ` ison
2019-05-05 0:52 ` Zelphir Kaltstahl
2019-05-05 2:18 ` Mark H Weaver
2019-05-05 12:08 ` Zelphir Kaltstahl
2019-05-05 20:14 ` Mark H Weaver
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=20190504174533.zx6qi5y67zlgidld@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).