unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Francis Litterio <franl@world.std.com>
Subject: Re: CVS Emacs list-buffer-noselect calls set-window-buffer, displays every buffer briefly!
Date: Sat, 04 Sep 2004 15:40:04 -0400	[thread overview]
Message-ID: <u4qmdrf88.fsf@world.std.com> (raw)
In-Reply-To: <87oekmxw5f.fsf@eos.franken.de> (Stephan Stahl's message of "04 Sep 2004 10:42:36 +0200")

Stephan Stahl wrote:

> Kevin Rodgers writes:
>
>> But you have not only selected the buffer, you have modified the
>> buffer-window correspondence, and the doc string hints that you might
>> have forced a redisplay:
> [...]
>> Does replacing (progn (set-window-buffer ...) ...) with
>> (with-current-buffer (set-buffer buffer) ...) work?
>
> No that does not work.  Inside the loop that creates the buffer list
> is a (with-current-buffer buffer).  The additional (set-buffer buffer)
> you suggested does not make a difference.

If, in order to read text from the mode line for every buffer, we must
force the mode line for every buffer to be redisplayed (along with the
buffer itself), then _preventing_ redisplay from happening in this code
will prevent the code from reading text from the mode line of every
buffer, which was its original goal.

IMHO, briefly displaying every buffer is an unacceptable price to pay to
be able to read the mode line for every buffer.
--
Francis Litterio
franl@world.std.com
http://world.std.com/~franl/
GPG and PGP public keys available on keyservers.

  reply	other threads:[~2004-09-04 19:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 18:59 CVS Emacs list-buffer-noselect calls set-window-buffer, displays every buffer briefly! Francis Litterio
2004-09-02 19:57 ` Stefan Monnier
2004-09-02 20:07   ` Francis Litterio
2004-09-02 20:48     ` Stefan Monnier
2004-09-03  6:27       ` Stephan Stahl
2004-09-03 11:49         ` Francis Litterio
2004-09-04  3:28           ` Richard Stallman
2004-09-03 18:54         ` Kevin Rodgers
2004-09-04  8:42           ` Stephan Stahl
2004-09-04 19:40             ` Francis Litterio [this message]
2004-09-04 22:12           ` Richard Stallman
2004-09-03 19:15       ` Francis Litterio
  -- strict thread matches above, loose matches on Subject: below --
2004-09-05  5:12 Richard Stallman
2004-09-07 15:42 ` Francis Litterio
2004-09-08  0:22   ` Richard Stallman
2004-09-08 14:36 ` Francis Litterio
2004-09-09  4:02   ` Richard Stallman
2004-09-09 15:46     ` Francis Litterio
2004-09-08 15:02 ` Francis Litterio
2004-09-08 16:20   ` Kevin Rodgers
2004-09-08 18:21     ` Francis Litterio
2004-09-09  4:03       ` Richard Stallman
2004-09-09  8:23       ` Stephan Stahl
2004-09-09 15:41         ` Francis Litterio
2004-09-09 16:13           ` Stephan Stahl
2004-09-09 15:45         ` Richard 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=u4qmdrf88.fsf@world.std.com \
    --to=franl@world.std.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).