From: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: redisplay-dont-pause does not work
Date: Thu, 01 Jun 2006 11:44:27 +0200 [thread overview]
Message-ID: <85k681dxc4.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3d5dxs16a.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Mon, 29 May 2006 10:08:45 +0200")
storm@cua.dk (Kim F. Storm) writes:
> Richard Stallman <rms@gnu.org> writes:
>
>> Thanks. Does this do it?
>
> Obviously not, as the variable is named redisplay_dont_pause.
>
> Try this:
>
> *** dispnew.c 01 May 2006 16:16:58 -0400 1.363
> --- dispnew.c 28 May 2006 19:07:02 -0400
> ***************
> *** 6405,6411 ****
> {
> swallow_events (display);
>
> ! if (detect_input_pending_run_timers (display) || !NILP (Vexecuting_kbd_macro))
> return Qnil;
>
> if (initial_display)
> --- 6406,6415 ----
> {
> swallow_events (display);
>
> ! if ((detect_input_pending_run_timers (display)
> ! && !redisplay_dont_pause)
> ! || !NILP (Vexecuting_kbd_macro))
> !
> return Qnil;
>
> if (initial_display)
This works as documented in the manual. The effect with a non-zero
argument to sit-for is that redisplay happens immediately, then the
wait is commenced until (or unless) input is available. Which appears
natural enough. I propose checking this change in. It might be worth
mentioning redisplay-dont-pause in the DOC string of sit-for. If
people agree, I could write something for there.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-06-01 9:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 10:52 redisplay-dont-pause does not work David Kastrup
2006-05-26 2:21 ` Richard Stallman
2006-05-26 7:19 ` David Kastrup
2006-05-27 3:36 ` Richard Stallman
2006-05-27 6:49 ` David Kastrup
2006-05-28 3:18 ` Richard Stallman
2006-05-28 7:47 ` David Kastrup
2006-05-29 6:38 ` Richard Stallman
2006-05-29 8:08 ` Kim F. Storm
2006-06-01 9:44 ` David Kastrup [this message]
2006-06-01 12:11 ` Eli Zaretskii
2006-06-01 13:52 ` Kim F. Storm
2006-06-01 20:22 ` David Kastrup
2006-06-05 9:00 ` Lars Hansen
2006-06-05 9:05 ` David Kastrup
2006-06-05 9:19 ` Lars Hansen
2006-06-05 9:34 ` Slawomir Nowaczyk
2006-06-05 9:38 ` David Kastrup
2006-06-05 21:26 ` Kim F. Storm
2006-06-06 8:21 ` Lars Hansen
2006-06-06 9:47 ` Kim F. Storm
2006-06-06 9:58 ` David Kastrup
2006-06-06 11:40 ` Kim F. Storm
2006-06-09 11:50 ` David Kastrup
2006-06-13 23:04 ` Kim F. Storm
2006-06-06 12:44 ` Lars Hansen
2006-06-05 9:38 ` Lars Hansen
2006-06-05 21:31 ` Richard Stallman
2006-06-06 8:38 ` Kim F. Storm
2006-05-27 8:24 ` Lars Hansen
2006-05-27 11:28 ` Eli Zaretskii
2006-05-27 14:14 ` Stefan Monnier
2006-05-27 14:21 ` David Kastrup
2006-05-27 20:57 ` Kim F. Storm
2006-05-27 21:22 ` David Kastrup
2006-05-27 22:54 ` Kim F. Storm
2006-05-27 23:01 ` David Kastrup
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=85k681dxc4.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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).