From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Todor Kondić" <tk.code@protonmail.com>
Cc: "help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: Re: Fonts do not work with multiple profiles (fontconfig) and a proposed workaround
Date: Thu, 17 Dec 2020 15:41:27 -0500 [thread overview]
Message-ID: <87k0tggo7c.fsf@gmail.com> (raw)
In-Reply-To: <4qtqn61QUsVPmKV144g0dSsr55C8gea2B86SsGVSQpRzuKr4far0---GZx-aMqv6SXBndbVQFIDHmbJKh9G5kTYTqGPw_xQW3KOWMdjBuvs=@protonmail.com> ("Todor Kondić"'s message of "Wed, 30 Sep 2020 08:21:12 +0000")
Hi,
Todor Kondić <tk.code@protonmail.com> writes:
>> Hi Todor,
>>
>> Indeed, this workaround does the trick.
>> Here is my ~/.config/fontconfig/fonts.conf:
>>
>> --8<---------------cut here---------------start------------->8---
>> <?xml version="1.0"?>
>> <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
>> <!-- /etc/fonts/fonts.conf file to configure system font access -->
>> <fontconfig>
>> <dir>~/.guix-extra-profiles/emacs/emacs/share/fonts</dir>
>> </fontconfig>
>> --8<---------------cut here---------------end--------------->8---
>>
>> Packages' content is static, it is not modifier upon install, which is
>> why the default etc/fonts/fonts.conf is pointing to constant locations.
>>
>> The solution to this bug, I believe, would be to add a post-install
>> hook that generates the fonts.conf file with the right entries.
>>
>> Cheers!
I think a proper fix would be contributing a patch to fontconfig so that
it honors XDG_DATA_DIRS to lookup its fonts.
Any takers?
Maxim
prev parent reply other threads:[~2020-12-17 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 14:30 Fonts do not work with multiple profiles (fontconfig) and a proposed workaround Todor Kondić
2020-09-30 7:59 ` Pierre Neidhardt
2020-09-30 8:21 ` Todor Kondić
2020-12-17 20:41 ` Maxim Cournoyer [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
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=87k0tggo7c.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=help-guix@gnu.org \
--cc=tk.code@protonmail.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).