unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Chong Yidong <cyd@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: window-next-buffers
Date: Thu, 24 Nov 2011 10:59:59 +0100	[thread overview]
Message-ID: <4ECE159F.8080300@gmx.at> (raw)
In-Reply-To: <878vn67y0l.fsf@gnu.org>

 > IIUC, the functions window-next-buffers and set-window-next-buffers (and
 > the corresponding next_buffers slot) exist for navigating "forward" in
 > the window history list, via switch-to-next-buffer, after doing
 > switch-to-prev-buffer.
 >
 > Maintaining separate prev-history and next-history lists is not very
 > Emacs-y.  Why isn't this a ring?

Because `window-previous-buffers' returns a list of <buffer window-start
pos> triples where the latter two are markers and `window-next-buffers'
a plain list of buffers.  Maintaining markers is expensive, so I wanted
to reduce the overhead for the next buffers part of the list.

martin



  parent reply	other threads:[~2011-11-24  9:59 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 ` martin rudalics [this message]
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             ` window-next-buffers Juri Linkov
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=4ECE159F.8080300@gmx.at \
    --to=rudalics@gmx.at \
    --cc=cyd@gnu.org \
    --cc=emacs-devel@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).