From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Patterson <andrewpatt7@gmail.com>
Cc: conses <contact@conses.eu>,
62806@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#62806] [PATCH] gnu: home: services: fontutils: Add support for SXML fragments.
Date: Mon, 24 Apr 2023 22:41:10 +0200 [thread overview]
Message-ID: <87o7nd109l.fsf@gnu.org> (raw)
In-Reply-To: <20230413034059.5585-1-andrewpatt7@gmail.com> (Andrew Patterson's message of "Wed, 12 Apr 2023 23:40:59 -0400")
Hi,
Andrew Patterson <andrewpatt7@gmail.com> skribis:
> * gnu/home/services/fontutils.scm (add-fontconfig-config-file): Add
> support for adding arbitrary SXML configuration into fonts.conf;
> * doc/guix.texi (Fonts Services): Update the documentation.
> ---
> One of the main reasons I haven't started using guix home is that I use
> fonts.conf for setting default fonts, which guix home doesn't work with.
> This patch fixes that issue, by letting you add arbitrary XML to
> fonts.conf via SXML.
Nice! You’re the third person looking into this, which shows there’s a
real need. :-)
https://issues.guix.gnu.org/62145
https://issues.guix.gnu.org/57963
I like that your patch is simple (it doesn’t try to do anything beyond
serializing SXML); perhaps there are ideas to borrow from the patch by
Taiju HIGASHI?
OTOH it’s less convenient to use for someone who’s not familiar with the
XML schema of ‘fonts.conf’ than what the patch by conses does.
I think we should really move forward on this. Because it’s not
invasive, this patch sounds like the path of least resistance.
What are your thoughts, people? What should we choose? :-)
Ludo’.
next prev parent reply other threads:[~2023-04-25 1:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 3:40 [bug#62806] [PATCH] gnu: home: services: fontutils: Add support for SXML fragments Andrew Patterson
2023-04-24 20:41 ` Ludovic Courtès [this message]
2023-04-24 23:24 ` Andrew Patterson
2023-05-11 12:34 ` Ludovic Courtès
2023-05-12 6:45 ` Andrew Tropin
2023-05-18 9:11 ` Miguel Ángel Moreno
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=87o7nd109l.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=62806@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=andrewpatt7@gmail.com \
--cc=contact@conses.eu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.