From: "Gennady Uraltsev" <gennady.uraltsev@gmail.com>
Cc: 40384@debbugs.gnu.org
Subject: bug#40384: 26.3; [Windows10] variable-pitch-mode is slow to redraw
Date: Wed, 8 Apr 2020 11:30:22 -0400 [thread overview]
Message-ID: <000201d60dba$9eb50570$dc1f1050$@gmail.com> (raw)
In-Reply-To: <834ku1xd7g.fsf@gnu.org>
Hello,
None of the suggested fixes have any impact. I just did a clean reinstall of
my OS (Windows 10 Enterprise 10.0.18363 Build 18363) and the issue is
present still. Should we try to investigate the issue?
I have another PC on which I am going to be reinstalling windows soon. I
will check there and report back. (To see if it is hardware or software
related or a combination of the two...)
Best,
Gennady
On April 3, 2020 03:04:19 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: <gennady.uraltsev@gmail.com>
>> Cc: <40384@debbugs.gnu.org>
>> Date: Thu, 2 Apr 2020 18:29:07 -0400
>>
>> By default the font that gets used is
>>
>> display: by this font (glyph code)
>>
>> uniscribe:-outline-Arial-normal-normal-normal-sans-20-*-*-*-p-*-iso8859-1
>> (#x03)
>
> That's the same font I get, but I see no slowdown.
>
> Thanks for the profile, it says that somehow redrawing even ASCII
> characters (if you indeed did that with the comment in *scratch*
> copied many times, as your recipe says) is somehow very expensive on
> your system.
>
> Does it help to customize inhibit-compacting-font-caches to non-nil?
next prev parent reply other threads:[~2020-04-08 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 0:06 bug#40384: 26.3; [Windows10] variable-pitch-mode is slow to redraw gennady.uraltsev
2020-04-02 14:40 ` Eli Zaretskii
2020-04-02 22:29 ` gennady.uraltsev
2020-04-03 7:04 ` Eli Zaretskii
2020-04-08 15:30 ` Gennady Uraltsev [this message]
2020-04-08 15:38 ` Eli Zaretskii
2021-12-05 1:16 ` Lars Ingebrigtsen
2022-01-21 13:38 ` Lars Ingebrigtsen
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='000201d60dba$9eb50570$dc1f1050$@gmail.com' \
--to=gennady.uraltsev@gmail.com \
--cc=40384@debbugs.gnu.org \
/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).