From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 24560@debbugs.gnu.org, thecybershadow@gmail.com
Subject: bug#24560: 25.1; With `--font 7x13', wrong font is used for Unicode characters
Date: Sun, 17 Nov 2019 20:25:23 +0200 [thread overview]
Message-ID: <831ru65pik.fsf@gnu.org> (raw)
In-Reply-To: <8736em5qrh.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 17 Nov 2019 18:58:26 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: thecybershadow@gmail.com, 24560@debbugs.gnu.org
> Date: Sun, 17 Nov 2019 18:58:26 +0100
>
> So if somebody says explicitly --without-xft, then HAVE_XFT won't be
> "yes", and we set HAVE_FREETYPE to "no" without checking. And harfbuzz
> depends on HAVE_FREETYPE being "yes", so harfbuzz depends on xft being
> available, too.
>
> Is this correct behaviour?
Maybe I'm simply misremembering, and HarfBuzz does need xft.
> In addition, I think the configure script should fail if you say
> --with-harfbuzz and harfbuzz isn't available.
Probably.
next prev parent reply other threads:[~2019-11-17 18:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 16:34 bug#24560: 25.1; With `--font 7x13', wrong font is used for Unicode characters Vladimir Panteleev
2016-09-28 20:16 ` Eli Zaretskii
2016-09-28 21:58 ` Vladimir Panteleev
2016-09-29 15:30 ` Eli Zaretskii
2016-09-29 16:33 ` Vladimir Panteleev
2016-10-08 13:07 ` Eli Zaretskii
2016-10-15 14:10 ` Eli Zaretskii
2016-11-18 8:48 ` Eli Zaretskii
2019-11-17 7:21 ` Lars Ingebrigtsen
2019-11-17 13:10 ` Vladimir Panteleev
2019-11-17 16:10 ` Eli Zaretskii
2019-11-17 16:26 ` Lars Ingebrigtsen
2019-11-17 17:07 ` Eli Zaretskii
2019-11-17 17:09 ` Lars Ingebrigtsen
2019-11-17 17:58 ` Lars Ingebrigtsen
2019-11-17 18:25 ` Eli Zaretskii [this message]
2019-11-17 18:33 ` Lars Ingebrigtsen
2019-11-17 21:05 ` Robert Pluim
2019-11-18 9:19 ` Lars Ingebrigtsen
2022-04-23 14:02 ` Lars Ingebrigtsen
2022-04-23 15:17 ` Vladimir Panteleev
2019-11-17 19:05 ` Lars Ingebrigtsen
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=831ru65pik.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24560@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=thecybershadow@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.