From: Eli Zaretskii <eliz@gnu.org>
To: Adam Edge <baronedge@airmail.cc>
Cc: 49555@debbugs.gnu.org
Subject: bug#49555: 28.0.50; height display property causes text to render with incorrect spacing
Date: Sat, 17 Jul 2021 15:05:19 +0300 [thread overview]
Message-ID: <83a6ml403k.fsf@gnu.org> (raw)
In-Reply-To: <8b780fd8-9fce-e9e7-a2a1-38a0e327a11a@airmail.cc> (message from Adam Edge on Wed, 14 Jul 2021 19:00:25 +0300)
> From: Adam Edge <baronedge@airmail.cc>
> Date: Wed, 14 Jul 2021 19:00:25 +0300
>
> Another thing I've noticed is that when I just did the (set-face-attribute)
> part without (set-frame-font) and opened a new frame, the frame's font was
> the same as the one with incorrect letter spacing. When I did
> M-x describe-font RET, this is what I got in the `full name' line:Fira
> Code:pixelsize=14:foundry=CTDB:weight=normal:slant=normal:width=normal:spacing=90:scalable=true
> And the font loaded is: /usr/share/fonts/fira-code/FiraCode-Medium.ttf
> After doing the (set-frame-font), the font returned to the desired
> spacing. The `full-name' line in describe-font now is: Fira
> Code:pixelsize=14:foundry=CTDB:weight=normal:slant=normal:width=normal:spacing=100:scalable=true
> And the font loaded now is:
> /home/aedge/.local/share/fonts/FiraCode-Retina.ttf I suppose removing
> the system font should fix my problem here, and the issue can be closed,
> but why does the font change when '(height 1) is specified?
Good question. I don't really know the answer, but maybe that's
because the original font has a slightly different height?
next prev parent reply other threads:[~2021-07-17 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 22:27 bug#49555: 28.0.50; height display property causes text to render with incorrect spacing Adam Edge
2021-07-14 12:55 ` Eli Zaretskii
2021-07-14 16:00 ` Adam Edge
2021-07-14 16:05 ` Adam Edge
2021-07-17 12:05 ` Eli Zaretskii [this message]
2021-07-17 12:15 ` Eli Zaretskii
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=83a6ml403k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49555@debbugs.gnu.org \
--cc=baronedge@airmail.cc \
/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).