unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: redisplay-dont-pause does not work
Date: Sat, 27 May 2006 16:21:03 +0200	[thread overview]
Message-ID: <8564jrlfao.fsf@lola.goethe.zz> (raw)
In-Reply-To: <jwvirnrlfqq.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 27 May 2006 10:14:35 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> IMO changing the code is best. Otherwise, IIUC, there is no way one can
>>> force redisplay from a lisp program.
>
>> I think we should define what does ``force redisplay'' mean, before we
>> decide how to provide such a feature.  Does it mean redisplay
>> everything (i.e. every window on every frame)?  Or just the current
>> frame, or maybe just the current window?  (The latter should be
>> available with "C-l", I think.)  Do we want to let Lisp programs
>> specify what they want redisplayed, perhaps?
>
> I think we have to distinguish between a redisplay that does a "redraw" and
> one that does what the toplevel loop normally.  The "redraw" does call for
> a specification of what to redraw, but the normal toplevel redisplay doesn't
> (it just looks for things that have changed since the last "redisplay").
> For redraw, we already have redraw-display and redraw-frame and
> redraw-modeline, so I think we're set.

Disagree.  Those _clear_ the respective frame and mark it as to be
redrawn, but don't actually do the redraw.  Even if one _could_ use
them for forcing a redraw immediately, it would cause unnecessary
flicker.

> For forcing the display to be updated OTOH only sit-for is available
> and it's not reliable.

Well, then maybe one should try making it do what the docs claim?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2006-05-27 14:21 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
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 [this message]
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=8564jrlfao.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=eliz@gnu.org \
    --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).