From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: window-next-buffers Date: Thu, 24 Nov 2011 10:59:59 +0100 Message-ID: <4ECE159F.8080300@gmx.at> References: <878vn67y0l.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1322128821 31847 80.91.229.12 (24 Nov 2011 10:00:21 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 24 Nov 2011 10:00:21 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 24 11:00:17 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RTW6J-00048m-Iv for ged-emacs-devel@m.gmane.org; Thu, 24 Nov 2011 11:00:15 +0100 Original-Received: from localhost ([::1]:38349 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RTW6F-0006wg-I1 for ged-emacs-devel@m.gmane.org; Thu, 24 Nov 2011 05:00:11 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:37841) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RTW6C-0006v3-0T for emacs-devel@gnu.org; Thu, 24 Nov 2011 05:00:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RTW66-0006ui-Ax for emacs-devel@gnu.org; Thu, 24 Nov 2011 05:00:07 -0500 Original-Received: from mailout-de.gmx.net ([213.165.64.23]:38244) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RTW65-0006uG-U5 for emacs-devel@gnu.org; Thu, 24 Nov 2011 05:00:02 -0500 Original-Received: (qmail invoked by alias); 24 Nov 2011 09:59:59 -0000 Original-Received: from 62-47-39-221.adsl.highway.telekom.at (EHLO [62.47.39.221]) [62.47.39.221] by mail.gmx.net (mp043) with SMTP; 24 Nov 2011 10:59:59 +0100 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX189CfAESjU9xVRtT4nZ8GgUbKrTY99JckYSwaB6XQ 8dl6C9qKDWo5t1 User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: <878vn67y0l.fsf@gnu.org> X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 213.165.64.23 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:146196 Archived-At: > 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 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