From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: greselin.andrea@gmail.com, 39082@debbugs.gnu.org
Subject: bug#39082: Inconsolata v3.000 has too wide spacing
Date: Mon, 13 Jan 2020 17:43:14 +0100 [thread overview]
Message-ID: <m2o8v7tihp.fsf@gmail.com> (raw)
In-Reply-To: <83zher5nyt.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 13 Jan 2020 18:18:50 +0200")
>>>>> On Mon, 13 Jan 2020 18:18:50 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: Andrea Greselin <greselin.andrea@gmail.com>, 39082@debbugs.gnu.org
>> Date: Mon, 13 Jan 2020 10:27:32 +0100
>>
Eli> So the question now becomes how come we get such a large value. Looks
Eli> like we somehow use the space-width value instead of the character
Eli> glyph's width, not sure why. I guess stepping through the code I've
Eli> shown from xdisp.c is still necessary to understand this.
>>
>> I can reproduce this, but I donʼt know how much effort we should spend
>> getting to the bottom of it: a Cairo-enabled build (ie !XFT) does not
>> have this problem.
Eli> So I guess this is some kind of Xft bug? In that case, I think it
Eli> would be enough to describe the Cairo workaround in etc/PROBLEMS, and
Eli> close the bug with that.
Itʼs either a bug or a limitation in the Xft interface. I see the
width of characters coming back from XftGlyphExtents as 26, with all
the other metrics as 0, so I donʼt think thereʼs much we can do.
Andrea, does building emacs-27 configure '--with-cairo' fix this for
you?
Robert
next prev parent reply other threads:[~2020-01-13 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 10:03 bug#39082: Inconsolata v3.000 has too wide spacing Andrea Greselin
2020-01-12 15:37 ` Eli Zaretskii
2020-01-12 16:56 ` Eli Zaretskii
2020-01-12 17:52 ` Eli Zaretskii
2020-01-12 18:17 ` Andrea Greselin
2020-01-12 18:44 ` Eli Zaretskii
2020-01-13 9:27 ` Robert Pluim
2020-01-13 16:18 ` Eli Zaretskii
2020-01-13 16:43 ` Robert Pluim [this message]
2020-01-13 16:56 ` Andrea Greselin
2020-01-13 17:03 ` Robert Pluim
2020-01-13 17:26 ` Eli Zaretskii
2020-01-14 9:52 ` Robert Pluim
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=m2o8v7tihp.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=39082@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=greselin.andrea@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.