From: Juri Linkov <juri@jurta.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Buffer listing in multiple frames/ttys
Date: Wed, 07 Dec 2005 02:52:19 +0200 [thread overview]
Message-ID: <87pso9wvjo.fsf@jurta.org> (raw)
In-Reply-To: <lorentey.m.other.87vey2wg1m.elte@walrus.fnord.hu> (Károly Lőrentey's message of "Tue, 06 Dec 2005 13:44:53 +0100")
> I note that `bury-buffer' removes the buffer from the frame-local
> buffer lists of all frames, not just the selected one. This is an
> unwanted side-effect in this case, as we want the effects of
> `next-buffer' to remain frame-local. I propose to add an optional
> parameter to `bury-buffer' to support this.
I think this change should be made for all invocations of `bury-buffer',
not only from `next-buffer'. Also I think recoding a buffer to the
new frame parameter should be made in `bury-buffer' instead of
`next-buffer'. And so there is no need for a new optional parameter.
Some commands call `bury-buffer' directly, and it would be good to
record their buffers in the frame-local parameter.
> I appended to the end of this message enhanced versions of
> `next-buffer' and `prev-buffer' that eliminate this problem by
> maintaining a new auxiliary frame-local buffer list, called
> `previous-buffer-list'. `next-buffer' prepends the old buffer to this
> list, and `prev-buffer' searches this list first; otherwise the two
> functions behave as in CVS.
These functions are much better than previous versions, but still
don't work correctly without changes in `bury-buffer'.
Instead of introducing a new frame parameter `previous-buffer-list'
what do you think about reusing the existing frame parameter `buffer-list'?
It could have a special marker delimiting a list of frame's "next" visited
buffers and "previous" visited buffers. A nil value could serve as
such special marker. So for example, (frame-parameter nil 'buffer-list)
could contain:
(#<buffer *b+1*> #<buffer *b+2*> nil #<buffer *b-2*> #<buffer *b-1*>)
where buffers until `nil' are buffers added by `switch-to-buffer'
(i.e. the same buffers that are currently recorded in this parameter),
and buffers after `nil' are buffers added by `bury-buffer'.
Then some functions should be changed to understand this new format of
the frame parameter `buffer-list'.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-12-07 0:52 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
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 [this message]
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=87pso9wvjo.fsf@jurta.org \
--to=juri@jurta.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).