From: Eli Zaretskii <eliz@gnu.org>
To: gennady.uraltsev@gmail.com
Cc: 40384@debbugs.gnu.org
Subject: bug#40384: 26.3; [Windows10] variable-pitch-mode is slow to redraw
Date: Thu, 02 Apr 2020 17:40:55 +0300 [thread overview]
Message-ID: <83pncqx85k.fsf@gnu.org> (raw)
In-Reply-To: <000201d60882$951fd3b0$bf5f7b10$@gmail.com> (gennady.uraltsev@gmail.com)
> From: <gennady.uraltsev@gmail.com>
> Date: Wed, 1 Apr 2020 20:06:38 -0400
>
> I am trying to emacs under Windows 10. variable-pitch-mode is insanely slow
> in redrawing the screen. With a clean emacs.d I opened a text file and tried
> pressing the down arrow. The cursor gets redisplayed every 10 lines or so
> and emacs is very sluggish. It is interesting that this DOES NOT happen with
> a normal, fixed-pitch, font and also does NOT happen if I set the default
> font to be a variable pitch one e.g. "Segoe UI". It only happens with
> variable-pitch-mode.
I don't think I can reproduce this.
Which font is used on your system when you turn on
variable-pitch-mode? (You can type "C-u C-x =" on a character to see
the font used to display it.)
> Attached are profiler results for moving down two pages worth of
> text.
Thanks, but you provided a "memory" profile, which is almost useless.
Please provide the "cpu" profile instead, and please show it in
human-readable form (after performing the measurement, type "M-x
profiler-report RET", then go to each top-level "+" sign and type "C-u
RET" to expand the profile; and finally paste the result into your
message and send it).
next prev parent reply other threads:[~2020-04-02 14:40 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 [this message]
2020-04-02 22:29 ` gennady.uraltsev
2020-04-03 7:04 ` Eli Zaretskii
2020-04-08 15:30 ` Gennady Uraltsev
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=83pncqx85k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40384@debbugs.gnu.org \
--cc=gennady.uraltsev@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).