From: Eli Zaretskii <eliz@gnu.org>
To: greselin.andrea@gmail.com
Cc: 39082@debbugs.gnu.org
Subject: bug#39082: Inconsolata v3.000 has too wide spacing
Date: Sun, 12 Jan 2020 19:52:40 +0200 [thread overview]
Message-ID: <83a76s7eaf.fsf@gnu.org> (raw)
In-Reply-To: <83d0bo7gwn.fsf@gnu.org> (message from Eli Zaretskii on Sun, 12 Jan 2020 18:56:08 +0200)
> Date: Sun, 12 Jan 2020 18:56:08 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 39082@debbugs.gnu.org
>
> > Date: Sun, 12 Jan 2020 17:37:58 +0200
> > From: Eli Zaretskii <eliz@gnu.org>
> > Cc: 39082@debbugs.gnu.org
> >
> > Sadly, I have no idea how to go about investigating this problem
> > further, maybe someone else does?
>
> One idea is to look at the character glyph metric we get from the font
> here:
An easier way to get at the character glyph metrics is like this:
M-: (font-get-glyphs (font-at 1) 1 2) RET
This should show the glyph metrics of the font glyph used to display
the character at buffer position 1. (Change 1 to any other buffer
position to report on a character there, and then change 2 to 1 more
than that position, for example 100 and 101 for the character at
buffer position 100.)
I'm mostly interested in the WIDTH element (the 5th element) of the
result, but maybe others will also show something important. It would
be also interesting to compare this with a font that is displayed
"normally".
Thanks.
next prev parent reply other threads:[~2020-01-12 17:52 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 [this message]
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
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=83a76s7eaf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39082@debbugs.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 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).