From: storm@cua.dk (Kim F. Storm)
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: Display slowness that is painful
Date: Fri, 03 Feb 2006 11:00:22 +0100 [thread overview]
Message-ID: <m3k6cciwy1.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1F4t73-0007JI-58@fencepost.gnu.org> (Richard M. Stallman's message of "Fri, 03 Feb 2006 00:04:01 -0500")
"Richard M. Stallman" <rms@gnu.org> writes:
> Thanks for writing that optimization. I figured some such simple fix
> would be possible. Please install your fix.
>
> What my experience has taught me is that cases of anomalous gross
> slowness often have a simple fix. Thus, before taking up the
> difficult question of whether major surgery is justified, it's a good
> idea to look for a fix like this one which does the job with a band-aid.
>
> (Yi-dong found a different way to apply a band-aid, but it assumes
> that the file was visited in Image mode, so it doesn't solve the whole
> problem. This change does, I think.)
While debugging this, I noticed that sometimes redisplay was (quite) fast,
while at other times, it was VERY slow.
I traced this to emacs starting to process SELECTION_REQUEST_EVENT
events after each redisplay round -- and consequently doing another
redisplay... So in effect it never seemed to reach a point where it
would actually update the display.
Doing M-: (setq redisplay-dont-pause t) RET made redisplay much
snappier in this specific case.
Perhaps we should have some form of timer associated with the
(default) redisplay-dont-pause == nil case, so that even if
input_pending, we will still update the display if the last completed
redisplay happened more than, say 2 seconds ago.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-02-03 10:00 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 22:31 Display slowness that is painful Richard Stallman
2006-01-31 5:10 ` Chong Yidong
2006-01-31 23:09 ` Richard M. Stallman
2006-02-01 1:25 ` Chong Yidong
2006-02-01 2:59 ` Stefan Monnier
2006-02-01 4:52 ` Chong Yidong
2006-02-01 5:15 ` Miles Bader
2006-02-02 6:02 ` Chong Yidong
2006-02-02 4:15 ` Richard M. Stallman
2006-02-02 4:50 ` Chong Yidong
2006-02-01 10:43 ` Andreas Schwab
2006-02-03 2:06 ` Kenichi Handa
2006-02-03 10:15 ` Andreas Schwab
2006-02-03 12:01 ` Kenichi Handa
2006-02-03 13:08 ` Andreas Schwab
2006-02-03 19:17 ` Eli Zaretskii
2006-02-03 23:34 ` Andreas Schwab
2006-02-07 1:41 ` Kenichi Handa
2006-02-02 4:16 ` Richard M. Stallman
2006-02-02 5:55 ` Chong Yidong
2006-02-02 6:12 ` Chong Yidong
2006-02-02 9:50 ` David Kastrup
2006-02-02 14:02 ` Stefan Monnier
2006-02-03 23:43 ` Richard M. Stallman
2006-02-02 11:33 ` Kim F. Storm
2006-02-03 1:50 ` Kenichi Handa
2006-02-03 9:55 ` Kim F. Storm
2006-02-04 18:27 ` Richard M. Stallman
2006-02-03 5:04 ` Richard M. Stallman
2006-02-03 10:00 ` Kim F. Storm [this message]
2006-02-03 23:01 ` Stefan Monnier
2006-02-05 0:16 ` Kim F. Storm
2006-02-04 18:27 ` Richard M. Stallman
2006-02-04 21:18 ` Kim F. Storm
2006-02-05 1:59 ` Stefan Monnier
2006-02-06 2:06 ` Richard M. Stallman
2006-02-06 8:22 ` Kim F. Storm
2006-02-07 6:06 ` Richard M. Stallman
2006-02-07 9:14 ` Kim F. Storm
2006-02-08 19:03 ` Richard M. Stallman
2006-02-09 9:20 ` Kim F. Storm
2006-02-09 20:10 ` Eli Zaretskii
2006-02-13 4:40 ` Richard M. Stallman
2006-02-13 4:40 ` Richard M. Stallman
2006-02-06 2:06 ` Richard M. Stallman
2006-02-06 8:19 ` Kim F. Storm
2006-02-06 8:45 ` Miles Bader
2006-02-06 10:34 ` Kim F. Storm
2006-02-07 6:06 ` Richard M. Stallman
2006-02-05 0:30 ` Miles Bader
2006-02-05 0:44 ` Kim F. Storm
2006-02-02 14:00 ` Stefan Monnier
2006-02-01 10:51 ` Andreas Schwab
2006-02-01 23:10 ` Chong Yidong
2006-02-02 4:16 ` Richard M. Stallman
2006-02-02 10:37 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2006-01-19 17:43 Richard Stallman
2006-01-31 5:07 ` Evil Boris
2006-01-11 18:58 Richard M. Stallman
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=m3k6cciwy1.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@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).