unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: Slawomir Nowaczyk <slawomir.nowaczyk.847@student.lu.se>,
	emacs-devel@gnu.org
Subject: Re: redisplay-dont-pause does not work
Date: Tue, 06 Jun 2006 11:47:36 +0200	[thread overview]
Message-ID: <m364jeipjb.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <44853B02.4040504@soem.dk> (Lars Hansen's message of "Tue, 06 Jun 2006 10:21:22 +0200")

Lars Hansen <lists@soem.dk> writes:

> Kim F. Storm wrote:
>
>>(defun redisplay-now (&optional object)
>>  "Force immediate display update of all windows.
>>If optional arg object is a frame, update display of that frame only.
>>If optional arg object is a window, update display of that window only.
>>If object is a buffer or buffer name, update display of all windows
>>displaying that buffer."
>>  ;; There is currently no way to update individual windows, so
>>  ;; update everything.
>>  (let ((redisplay-dont-pause t))
>>    (sit-for 0)))
>>  
>>
> This would be great IMO.


Thinking some more about this, I'm a bit puzzled about what specific
purpose anyone would have from doing this ...   

In most cases, if there are no changes to other parts of the frame,
redisplay will not spend time on updating them...  So if the concern
is that updating all windows/frames is performance related, I think
that's a non-issue.

And even if it _does_ redisplay all windows/frames, only the actual
changes to the display are actually propagated to the screen.


So I'm back to supporting the original proposal of having an explicit
"redisplay now" functionality ... but I propose to implement it as a
special call to sit-for: (sit-for t) or perhaps as
(sit-for 0 'redisplay-dont-pause).

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2006-06-06  9:47 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 [this message]
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=m364jeipjb.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=slawomir.nowaczyk.847@student.lu.se \
    /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).