unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts.
Date: Thu, 21 May 2020 01:35:10 +0200	[thread overview]
Message-ID: <CAJ3okZ0ejNNCzngyEde43rLDy9FcAEhC1HVa-MKem6PHUm282A@mail.gmail.com> (raw)
In-Reply-To: <87imgq9tcz.fsf@devup.no>

On Wed, 20 May 2020 at 23:41, Marius Bakke <mbakke@fastmail.com> wrote:

> Missing fonts in the manual is another known issue and was not clear
> from your initial message: <https://issues.guix.gnu.org/issue/41418>.

My initial message was on <http://issues.guix.gnu.org/issue/41282> and
not on #41418; I have never commented on.
I do not understand why you are saying "missing font in the manual"
because I have the fonts installed; especially font-dejavu (and
gs-fonts too).
Well, I do not understand neither how c81457a588 can work nicely and
not 23a59b180b with the exact same setup, if nothing has changed in
regard to font between these 2 parent commits of the last merge.

Last, I confirm that the commit
ab9de8cfb0525ef43668712ac898707f97f9a620 fixes the issue. Thank you.

Best regards,
simon


  reply	other threads:[~2020-05-20 23:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 14:50 [PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts Marius Bakke
2020-05-19 15:50 ` Leo Famulari
2020-05-20 11:28   ` Marius Bakke
2020-05-20 22:59     ` Leo Famulari
2020-05-20 22:00   ` Marius Bakke
2020-05-20 12:06 ` zimoun
2020-05-20 13:55   ` Marius Bakke
2020-05-20 21:03     ` zimoun
2020-05-20 21:41       ` Marius Bakke
2020-05-20 23:35         ` zimoun [this message]
2020-05-21 12:46           ` Marius Bakke

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=CAJ3okZ0ejNNCzngyEde43rLDy9FcAEhC1HVa-MKem6PHUm282A@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.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.
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).