From: lorentey@elte.hu (Lőrentey Károly)
Subject: Re: Buffer listing in multiple frames/ttys
Date: Tue, 29 Nov 2005 11:45:09 +0100 [thread overview]
Message-ID: <lorentey.g.e.devel.87veybhgwa.elte@walrus.fnord.hu> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICKEHACPAA.drew.adams@oracle.com> (Drew Adams's message of "Mon, 28 Nov 2005 15:12:47 -0800")
[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]
Drew Adams <drew.adams@oracle.com> writes:
> The default ordering is chronological, so, yes, the most recent
> buffer is always first. The relative order of the other buffers is
> not changed, however (currently).
>
> Your reordering goes beyond that - the change in order is confusing,
> unless one is thinking in terms of multiple buffers per frame and
> one knows about the new behavior.
Well, if there is any change in the relative order, then that implies
that the frames sometimes change what buffer they display. The
`buffer-list' frame parameter contains a chronological list of buffers
that were ever displayed in the frame. The new code will not change
the relative order of buffers in *Buffer List* unless this list has
more than one entry. But that would imply that the user does use
multiple buffers per frame, so arguably the new code can be useful.
How about that! :-)
I think we have spent too much time on this. I agree that there is no
point in having frame-local buffer lists when pop-up-frames is set to
t, so I propose in that case we continue to use the global
buffer-list, as before. However, the frame-local version does have
important benefits for the "thematic frame" people and when there are
multiple terminals, so let's keep it enabled when pop-up-frames is not
set.
> That means that the new behavior would need to be documented
> explicitly, or else people will not understand what they see.
I will do that, of course.
> Given that, I can't say I'm annoyed by your change. I was thinking
> of the (imagined) need to re-sort.
So, should I apply this patch or not? :-)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1027 bytes --]
Index: buff-menu.el
===================================================================
RCS file: /cvsroot/emacs/emacs/lisp/buff-menu.el,v
retrieving revision 1.95
diff -u -3 -p -r1.95 buff-menu.el
*** buff-menu.el 28 Nov 2005 14:36:06 -0000 1.95
--- buff-menu.el 29 Nov 2005 09:48:51 -0000
***************
*** 722,728 ****
(if (memq c '(?\n ?\s)) c underline))
header)))))
;; Collect info for every buffer we're interested in.
! (dolist (buffer (or buffer-list (buffer-list (selected-frame))))
(with-current-buffer buffer
(let ((name (buffer-name))
(file buffer-file-name))
--- 722,731 ----
(if (memq c '(?\n ?\s)) c underline))
header)))))
;; Collect info for every buffer we're interested in.
! (dolist (buffer (or buffer-list
! ;; Use the frame-local list when it makes sense.
! (buffer-list (and (not pop-up-frames)
! (selected-frame)))))
(with-current-buffer buffer
(let ((name (buffer-name))
(file buffer-file-name))
[-- Attachment #3: Type: text/plain, Size: 601 bytes --]
> [However, I have my own extension to the column-sorting that adds a
> Time column, which shows the `buffer-display-time'. If I sort on
> that column, will I need to re-sort? I don't know - is
> `buffer-display-time' what is used in your ordering? That's what my
> "Time" column uses.]
No, Emacs simply uses the above mentioned frame parameter together
with the global list to generate the frame-local ordering---it doesn't
mess with the recorded display time for this.
Therefore, I think that using the frame-local buffer-list should not
affect your sorting results.
--
Károly
[-- Attachment #4: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2005-11-29 10:45 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 20:25 Buffer listing in multiple frames/ttys Len Trigg
2005-11-24 21:44 ` Károly Lőrentey
2005-11-28 14:37 ` Lőrentey Károly
2005-11-28 17:16 ` Drew Adams
2005-11-28 18:24 ` Lőrentey Károly
2005-11-28 19:23 ` Drew Adams
2005-11-28 20:48 ` Lőrentey Károly
2005-11-28 23:12 ` Drew Adams
2005-11-29 0:15 ` Luc Teirlinck
2005-11-29 0:29 ` Drew Adams
2005-11-29 10:45 ` Lőrentey Károly [this message]
2005-11-29 15:36 ` Drew Adams
2005-11-29 18:43 ` Luc Teirlinck
2005-11-29 19:24 ` Drew Adams
2005-11-30 13:21 ` Lőrentey Károly
2005-11-29 18:12 ` Luc Teirlinck
2005-11-29 23:35 ` Luc Teirlinck
2005-11-29 23:55 ` Chong Yidong
2005-11-29 23:57 ` Chong Yidong
2005-11-30 0:20 ` Drew Adams
2005-12-02 21:09 ` Juri Linkov
2005-12-03 15:58 ` Richard M. Stallman
2005-12-03 17:03 ` Lőrentey Károly
2005-12-03 17:46 ` Juri Linkov
2005-12-04 21:18 ` Richard M. Stallman
2005-12-04 21:56 ` Juri Linkov
2005-12-05 4:33 ` Eli Zaretskii
2005-12-05 6:03 ` Juri Linkov
2005-12-05 16:38 ` Richard M. Stallman
2005-12-05 14:44 ` Károly Lőrentey
2005-12-05 21:32 ` Juri Linkov
2005-12-06 16:42 ` Richard M. Stallman
2005-12-06 1:43 ` Richard M. Stallman
2005-12-06 12:44 ` Károly Lőrentey
2005-12-07 0:52 ` Juri Linkov
2005-12-07 14:51 ` Károly Lőrentey
2005-12-07 21:29 ` Juri Linkov
2005-12-08 7:48 ` Juri Linkov
2005-12-08 14:26 ` Lőrentey Károly
2005-12-08 19:29 ` Richard M. Stallman
2005-12-08 21:56 ` Juri Linkov
2005-12-09 15:04 ` Richard M. Stallman
2005-12-09 20:04 ` Lőrentey Károly
2005-12-09 23:54 ` Juri Linkov
2005-12-10 16:18 ` Richard M. Stallman
2005-12-11 0:54 ` Juri Linkov
2005-12-11 16:49 ` Richard M. Stallman
2005-12-11 16:57 ` Károly Lőrentey
2005-12-11 16:53 ` Károly Lőrentey
2005-12-11 22:57 ` Richard M. Stallman
2005-12-12 12:56 ` Károly Lőrentey
2005-12-12 7:43 ` Juri Linkov
2005-12-07 17:07 ` Richard M. Stallman
2005-12-07 17:15 ` Károly Lőrentey
2005-12-08 4:53 ` Richard M. Stallman
2005-12-06 16:20 ` Drew Adams
2005-12-06 18:09 ` Lőrentey Károly
2005-12-07 16:54 ` Drew Adams
2005-12-07 21:29 ` Juri Linkov
2005-12-08 0:03 ` Drew Adams
[not found] <lorentey.g.e.devel.87hd9uff0k.elte@walrus.fnord.hu>
2005-11-30 16:33 ` Drew Adams
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=lorentey.g.e.devel.87veybhgwa.elte@walrus.fnord.hu \
--to=lorentey@elte.hu \
/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).