all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: , emacs-devel@gnu.org
Subject: Re: cairo now default?
Date: Tue, 28 Jan 2020 15:09:49 +0000	[thread overview]
Message-ID: <87pnf3vcqq.fsf@yandex.com> (raw)
In-Reply-To: <87tv4fvdwc.fsf@yandex.com> (Colin Baxter's message of "Tue, 28 Jan 2020 14:44:51 +0000")

>>>>> "Colin" == Colin Baxter <m43cap@yandex.com> writes:

>>>>> 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
    Colin> ./configure when there are is harfbuzz dev lib. The user
    Colin> who's always just done ./configure will see something
    Colin> different.

    >> PS Your CC is malformed: it has a stray comma in it.

    Colin> Yes, thanks. I haven't yet traced the reason.


I have a serious flat-finger problem today!! What I meant to type is 

"emacs -q" from ./configure --without-cairo looks different from "emacs
-q" from ./configure when there are is NO harfbuzz dev lib.

Best wishes,



  reply	other threads:[~2020-01-28 15:09 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 [this message]
2020-01-28 15:27                   ` Robert Pluim
2020-01-28 15:14                 ` Robert Pluim
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnf3vcqq.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@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.