From: Marco van Hulten <marco@hulten.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30655@debbugs.gnu.org
Subject: bug#30655: closed (Re: bug#30655: xset(1) not accepting symlink to font path)
Date: Sat, 03 Mar 2018 16:26:14 +0100 [thread overview]
Message-ID: <20180303162614.2fe6c3c5@jasniac.instanton> (raw)
In-Reply-To: <handler.30655.D30655.151999474622089.notifdone@debbugs.gnu.org>
Ludo'—
Je 2 mrt 12:46 skribis GNU:
> > diff --git a/doc/guix.texi b/doc/guix.texi
> > index 24db16761..35221ff94 100644
> > --- a/doc/guix.texi
> > +++ b/doc/guix.texi
> > @@ -1572,7 +1572,7 @@ To be able to use such full names for the
> > TrueType fonts installed in your Guix profile, you need to extend the
> > font path of the X server:
> > @example
> > -xset +fp ~/.guix-profile/share/fonts/truetype
> > +xset +fp $(dirname $(readlink -f ~/.guix-profile/share/fonts/truetype/fonts.dir))
> > @end example
>
> Actually commit 07ec349229 that I just pushed fixes this very line. So
> I guess we’re done?
I don't think so, because I just did a 'git pull', and found that the
old patch had been applied (the one with `readlink... that doesn't
work, instead of the above with $(dirname $(readlink...) which works.
Apropos, how often are the HTML pages generated from the repository and
put online?
—Marco
next prev parent reply other threads:[~2018-03-03 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 21:54 bug#30655: xset(1) not accepting symlink to font path Marco van Hulten
2018-03-01 16:52 ` Ludovic Courtès
2018-03-01 21:17 ` Marco van Hulten
2018-03-02 12:45 ` Ludovic Courtès
2018-03-01 17:47 ` Alex Kost
2018-03-01 21:27 ` Marco van Hulten
[not found] ` <handler.30655.D30655.151999474622089.notifdone@debbugs.gnu.org>
2018-03-03 15:26 ` Marco van Hulten [this message]
2018-03-04 21:41 ` bug#30655: closed (Re: bug#30655: xset(1) not accepting symlink to font path) Ludovic Courtès
2020-06-17 2:47 ` bug#30655: xset(1) not accepting symlink to font path Royce Strange
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=20180303162614.2fe6c3c5@jasniac.instanton \
--to=marco@hulten.org \
--cc=30655@debbugs.gnu.org \
--cc=ludo@gnu.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.
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).