From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: improving function "mode-line-unbury-buffer" in bindings.el Date: 18 Jul 2002 18:04:07 +0200 Sender: emacs-devel-admin@gnu.org Message-ID: <5xfzyhoweg.fsf@kfs2.cua.dk> References: <20020712.103500.40922275.tune@bg.wakwak.com> <200207141522.g6EFMRW20484@aztec.santafe.edu> <20020715.021323.100571771.tune@bg.wakwak.com> <200207161329.g6GDTOb22043@aztec.santafe.edu> <5xr8i3emlx.fsf@kfs2.cua.dk> <200207181456.g6IEu5W25120@aztec.santafe.edu> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1027004677 18573 127.0.0.1 (18 Jul 2002 15:04:37 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 18 Jul 2002 15:04:37 +0000 (UTC) Cc: tune@bg.wakwak.com, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17VCpX-0004pS-00 for ; Thu, 18 Jul 2002 17:04:35 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17VD1U-000878-00 for ; Thu, 18 Jul 2002 17:16:56 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17VCpM-0007XK-00; Thu, 18 Jul 2002 11:04:24 -0400 Original-Received: from mail.filanet.dk ([195.215.206.179]) by fencepost.gnu.org with smtp (Exim 3.35 #1 (Debian)) id 17VCoZ-0007Tt-00; Thu, 18 Jul 2002 11:03:35 -0400 Original-Received: from kfs2.cua.dk.cua.dk (kfs2.local.filanet.dk [192.168.1.182]) by mail.filanet.dk (Postfix) with SMTP id 4F8C47C016; Thu, 18 Jul 2002 15:03:33 +0000 (GMT) Original-To: rms@gnu.org In-Reply-To: <200207181456.g6IEu5W25120@aztec.santafe.edu> Original-Lines: 27 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:5860 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:5860 Richard Stallman writes: > Here is what is CLAIMED to happen with bury-buffer: > > When you use bury-buffer to bury the buffer in the selected window, > the NEXT buffer to be shown in the selected window is chosen with a > preference to show a buffer which has previously been shown in a > window. > > What I see in the code of Fother_buffer is that it prefers the buffers > that have been shown in this frame before. However, burying a buffer > removes it from the frame's buffer list (this is a recent bug fix). > So as you cycle in this way, the frame's buffer list will empty out > and you will indeed get all the non-hidden buffers. > > - doing bury-buffer once will bury xyz and show *scratch*, and > - doing bury-buffer again will bury *scratch* and show xyz. > > I get *Messages* the third time now. So do I (which is why I said "CLAIMED to happen" in my explanation). So with the recent change to bury-buffer, unbury-buffer now does the right thing I guess. -- Kim F. Storm http://www.cua.dk