unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Chong Yidong <cyd@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
	"Stephen J. Turnbull" <stephen@xemacs.org>,
	emacs-devel@gnu.org
Subject: Re: window-next-buffers
Date: Fri, 25 Nov 2011 21:02:00 +0200	[thread overview]
Message-ID: <87r50wkouv.fsf@mail.jurta.org> (raw)
In-Reply-To: <87wraotcg8.fsf@gnu.org> (Chong Yidong's message of "Sat, 26 Nov 2011 00:05:11 +0800")

>> Actually, I suspect it means that Yidong was right when he suggested a
>> ring.  Butnevermind....
>
> No, I was wrong: a ring isn't a good fit for the design, in which
> `switch-to-prev-buffer' (i) switches to the previous buffers displayed
> in the buffer, and (ii) after successive `switch-to-prev-buffer's reach
> the end of that list, the command moves on to other buffers in the
> buffer list which the window hadn't visited before.  If we used a ring,
> we'd never hit the end, so we'd never move on to (ii).

Then we need just one list of buffers (visited in the window)
and the pointer referencing the currently displayed buffer
(or a numeric index of the position of the currently displayed
buffer in the list of visited buffers).



  reply	other threads:[~2011-11-25 19:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24  7:58 window-next-buffers Chong Yidong
2011-11-24  9:24 ` window-next-buffers Chong Yidong
2011-11-24 10:07   ` window-next-buffers martin rudalics
2011-11-24  9:59 ` window-next-buffers martin rudalics
2011-11-24 19:00   ` window-next-buffers Juri Linkov
2011-11-25 10:15     ` window-next-buffers martin rudalics
2011-11-25 10:33       ` window-next-buffers Juri Linkov
2011-11-25 13:55         ` window-next-buffers martin rudalics
2011-11-25 15:11         ` window-next-buffers Stephen J. Turnbull
2011-11-25 16:05           ` window-next-buffers Chong Yidong
2011-11-25 19:02             ` Juri Linkov [this message]
2011-11-26  6:59               ` window-next-buffers Chong Yidong
2011-11-26 11:44               ` window-next-buffers martin rudalics

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=87r50wkouv.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=cyd@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    --cc=stephen@xemacs.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).