From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: greselin.andrea@gmail.com, 39082@debbugs.gnu.org
Subject: bug#39082: Inconsolata v3.000 has too wide spacing
Date: Mon, 13 Jan 2020 18:18:50 +0200 [thread overview]
Message-ID: <83zher5nyt.fsf@gnu.org> (raw)
In-Reply-To: <m2eew3vh8b.fsf@gmail.com> (message from Robert Pluim on Mon, 13 Jan 2020 10:27:32 +0100)
> 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.
So I guess this is some kind of Xft bug? In that case, I think it
would be enough to describe the Cairo workaround in etc/PROBLEMS, and
close the bug with that.
Thanks.
next prev parent reply other threads:[~2020-01-13 16:18 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 [this message]
2020-01-13 16:43 ` Robert Pluim
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
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=83zher5nyt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39082@debbugs.gnu.org \
--cc=greselin.andrea@gmail.com \
--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 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).