From: Robert Pluim <rpluim@gmail.com>
To: Colin Baxter <m43cap@yandex.com>
Cc: emacs-devel@gnu.org
Subject: Re: cairo now default?
Date: Tue, 28 Jan 2020 16:14:41 +0100 [thread overview]
Message-ID: <m2mua7ipem.fsf@gmail.com> (raw)
In-Reply-To: <87tv4fvdwc.fsf@yandex.com> (Colin Baxter's message of "Tue, 28 Jan 2020 14:44:51 +0000")
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
>>>>> On Tue, 28 Jan 2020 14:44:51 +0000, Colin Baxter <m43cap@yandex.com> said:
>>>>> Robert Pluim <rpluim@gmail.com> writes:
>>>>> On Tue, 28 Jan 2020 13:01:29 +0000, Colin Baxter <m43cap@yandex.com> said:
Colin> I was thinking of a rather more mundane reason. For example,
Colin> although Debian 9.11 has the right version of the harfbuzz
Colin> dev library, Debian 8.11 doesn't. To me, Debian 8.11 does
Colin> seem that old.
>> Debian stable is always pretty far behind, no? In any case, people
>> who donʼt have the right HarfBuzz library will just end up
>> continuing to use FLT like before, so nothing changes for them.
Colin> But this is not the case, surely. "emacs -q" from ./configure
Colin> --without-cairo looks different from "emacs -q" from ./configure when
Colin> there are is harfbuzz dev lib. The user who's always just done
Colin> ./configure will see something different.
Only if they then choose to use a font for which Xft gets things
wrong. If their existing font was fine (and not bitmapped), it will be
fine under Cairo.
Which of these two screenshots is --with-cairo, and which is without?
(both are using HarfBuzz)
[-- Attachment #2: emacs-1.png --]
[-- Type: image/png, Size: 9979 bytes --]
[-- Attachment #3: emacs-2.png --]
[-- Type: image/png, Size: 9914 bytes --]
next prev parent reply other threads:[~2020-01-28 15:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 10:13 cairo now default? Colin Baxter
2020-01-28 10:22 ` Robert Pluim
2020-01-28 11:21 ` Colin Baxter
2020-01-28 11:30 ` Robert Pluim
2020-01-28 11:49 ` Colin Baxter
2020-01-28 12:01 ` Robert Pluim
2020-01-28 13:01 ` Colin Baxter
2020-01-28 13:09 ` Robert Pluim
2020-01-28 14:44 ` Colin Baxter
2020-01-28 15:09 ` Colin Baxter
2020-01-28 15:27 ` Robert Pluim
2020-01-28 15:14 ` Robert Pluim [this message]
2020-01-28 16:24 ` Colin Baxter
2020-01-28 16:37 ` Robert Pluim
2020-01-28 16:47 ` Colin Baxter
2020-01-28 16:55 ` Robert Pluim
2020-01-28 17:02 ` Yuri Khan
2020-01-28 17:32 ` Yuri Khan
2020-01-28 17:43 ` Yuri Khan
2020-01-29 8:30 ` Robert Pluim
2020-01-29 10:11 ` YAMAMOTO Mitsuharu
2020-01-29 10:54 ` Robert Pluim
2020-01-28 18:44 ` Colin Baxter
2020-01-28 17:49 ` Robert Pluim
2020-01-28 20:33 ` Colin Baxter
2020-01-29 11:21 ` Robert Pluim
2020-01-29 14:07 ` Colin Baxter
2020-01-28 13:10 ` Colin Baxter
2020-01-28 20:06 ` James Cloos
2020-01-29 8:45 ` Robert Pluim
2020-01-28 14:08 ` Eric S Fraga
2020-01-28 14:58 ` Robert Pluim
2020-01-29 6:53 ` Fraga, Eric
2020-01-29 10:57 ` Eric S Fraga
2020-02-01 15:42 ` Problems with SourceCodeVariable [Re: " Madhu
2020-02-03 9:25 ` Robert Pluim
2020-02-04 6:14 ` Tassilo Horn
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2mua7ipem.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=m43cap@yandex.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/emacs.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).