From: Colin Baxter <m43cap@yandex.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: , Robert Pluim <rpluim@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: cairo now default?
Date: Tue, 28 Jan 2020 18:44:11 +0000 [thread overview]
Message-ID: <87d0b3v2tg.fsf@yandex.com> (raw)
In-Reply-To: <CAP_d_8U2wK6ucnHmGYxhDg_rTY3170snawXWE6Dv7pCAMmy6Rg@mail.gmail.com> (Yuri Khan's message of "Wed, 29 Jan 2020 00:32:52 +0700")
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
>>>>> Yuri Khan <yuri.v.khan@gmail.com> writes:
> On Wed, 29 Jan 2020 at 00:02, Yuri Khan <yuri.v.khan@gmail.com> wrote:
>> For the record, I’m strongly in the slight hinting camp, and
>> would/will be much annoyed if/when Emacs decides to use strong
>> hinting despite my configuration.
> Also, I have just built Emacs 28.0.50 from Git master, with Cairo
> and Harfbuzz, and on my system and my configuration it renders
> slightly hinted just fine.
On another machine with Harfbuzz, and using M-x describe-char on the
first T in the scratch buffer:
A. With Harfbuzz but without cairo using "./configure --without-cairo <RET>"
xfthb:-unknown-DejaVu Sans Mono-normal-normal-normal-*-15-*-*-*-m-0-iso10646-1 (#x37)
This gives me the "without-cairo.png".
B. With Harfbuzz and cairo, using "./configure <RET>"
ftcrhb:-unknown-DejaVu Sans Mono-normal-normal-normal-*-15-*-*-*-m-0-iso10646-1 (#x37)
This gives me the "with-cairo.png".
Best wishes,
Colin.
P.S. Sorry about my typos.
[-- Attachment #2: without-cairo.png --]
[-- Type: image/png, Size: 99912 bytes --]
[-- Attachment #3: with-cairo.png --]
[-- Type: image/png, Size: 85380 bytes --]
next prev parent reply other threads:[~2020-01-28 18:44 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
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 [this message]
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=87d0b3v2tg.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
--cc=yuri.v.khan@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 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).