From: Eli Zaretskii <eliz@gnu.org>
To: Klaus-Dieter Bauer <bauer.klaus.dieter@gmail.com>
Cc: 24918@debbugs.gnu.org
Subject: bug#24918: 25.1; Fonts can make Emacs grind to a halt
Date: Tue, 29 Nov 2016 19:47:32 +0200 [thread overview]
Message-ID: <83inr6xjnv.fsf@gnu.org> (raw)
In-Reply-To: <CANtbJLGr59kfGECtBYiwSB9pjv3POG36bh7LmA79E5nhhPV2Og@mail.gmail.com> (message from Klaus-Dieter Bauer on Tue, 29 Nov 2016 11:29:03 +0100)
> From: Klaus-Dieter Bauer <bauer.klaus.dieter@gmail.com>
> Date: Tue, 29 Nov 2016 11:29:03 +0100
> Cc: 24918@debbugs.gnu.org
>
> The issue occurs with the default fonts too ("emacs -Q"). On Windows that means `Courier New' for `default'
> and `Monospace' for `fixed-pitch', `Monospace Serif` for `fixed-pitch-serif' and `Arial` for `variable-pitch'.
>
> With these default settings, the `package-list-packages' buffer works mostly fine, but the info page `(cl)
> Structures' for instace does not. Using different fonts, e.g. `Linux Libertine Mono' or `Noto Mono', the issue
> becomes only more widespread.
>
> I detail, I noticed that the issue indeed does occur specifically when font substitution kicks in. In the info-page
> for `(cl) Structure' this occurs, because the "=>" is replaced by the unicode symbol "⇒", which is displayed in
> a different font; Sadly I can't figure out a way to identify the substituted font; It is definitely a variable-pitch font
> (the symbol is wider than the default font, such that characters are no longer vertically aligned with other
> lines).
That's very strange, because I see nothing similar on my systems.
As Clément points out, "C-u C-x =" will show the font that is used to
display those characters. Please tell what they are; they use Symbola
here (and that's how things should be, by default).
next prev parent reply other threads:[~2016-11-29 17:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 15:53 bug#24918: 25.1; Fonts can make Emacs grind to a halt Klaus-Dieter Bauer
2016-11-10 16:20 ` Clément Pit--Claudel
2016-11-10 17:12 ` Eli Zaretskii
2016-11-10 22:05 ` Klaus-Dieter Bauer
2016-11-11 8:01 ` Eli Zaretskii
[not found] ` <CANtbJLGuWhD8jUQt_KEz82kpuknemNR8u2G71fqTav2bfrR-1Q@mail.gmail.com>
[not found] ` <83lgwc96nn.fsf@gnu.org>
[not found] ` <CANtbJLGpF-ME-rKFfTwpU28oJDcGr2ww2vJhPUx2zxqnreOXpQ@mail.gmail.com>
2016-11-28 15:47 ` Eli Zaretskii
2016-11-29 10:29 ` Klaus-Dieter Bauer
2016-11-29 14:09 ` Clément Pit--Claudel
2016-11-29 17:47 ` Eli Zaretskii [this message]
2016-11-29 22:42 ` Klaus-Dieter Bauer
2016-11-30 3:42 ` Eli Zaretskii
2016-11-30 10:01 ` Klaus-Dieter Bauer
2016-11-30 15:00 ` Eli Zaretskii
2016-12-01 10:21 ` Klaus-Dieter Bauer
2016-12-01 17:31 ` Eli Zaretskii
2016-11-29 23:17 ` Alan Third
2016-11-30 15:09 ` 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=83inr6xjnv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24918@debbugs.gnu.org \
--cc=bauer.klaus.dieter@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).