From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Daniel Barclay Newsgroups: gmane.emacs.help Subject: letting *Man xxx* buffers appear when burying other buffers Date: Tue, 23 Jul 2002 15:40:32 -0400 Sender: help-gnu-emacs-admin@gnu.org Message-ID: <3D3DB130.A57BCD17@smart.net> References: <20020723185950.7493.9547.Mailman@fencepost.gnu.org> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1027453332 19993 127.0.0.1 (23 Jul 2002 19:42:12 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 23 Jul 2002 19:42:12 +0000 (UTC) Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17X5Xu-0005CM-00 for ; Tue, 23 Jul 2002 21:42:11 +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 17X5X9-0004SQ-00; Tue, 23 Jul 2002 15:41:23 -0400 Original-Received: from gemini.smart.net ([207.176.80.109]) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17X5WK-0004L1-00 for ; Tue, 23 Jul 2002 15:40:32 -0400 Original-Received: from smart.net (IDENT:501@dsb.smart.net [216.253.158.250]) by gemini.smart.net (8.9.1/8.9.1) with ESMTP id PAA19613; Tue, 23 Jul 2002 15:40:30 -0400 X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19-ide i586) X-Accept-Language: en Original-To: help-gnu-emacs@gnu.org Errors-To: help-gnu-emacs-admin@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.help:696 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:696 In GNU Emacs 20.7.2, the bury-buffer command treats manual-page buffers (e.g., *Man xxx*) inconsistently. Specifically, if you create a manual-page buffer, switch to some other buffer in that window, and then do: M-x bury-buffer RET you don't get back to the first buffer. (In other cases, you would get back to where you were first.) How can I eliminate the special-case behavior? (Is there any configuration variable to set? How can I find the elisp code for a command?) (Is there any chance that anyone else would agree that this "feature" is a bug? (Or its being turned on by default. Or its being undocumented (in info and in describe-function). I can imagine that someone got tired of seeing related manual page buffers after deleting (or burying) source code buffers and added a special-case fix. However, behaving specially makes several things inconsistent. Usually, you can create or raise a number of buffers in sequence, and then use bury-buffer to return to each previous buffer. That was a very useful feature. There shouldn't be any reason you can't use that feature with manual page buffers. Behaving specially for manual pages is also inconsistent with delete-buffer: It used to be that both delete-buffer and bury-buffer left the previous buffer displayed. Now they diverge. If this feature is left in, could it at least by controlled by some configuration variable (a list of buffer types?)? (If it isn't already.) Thanks, Daniel -- Daniel Barclay dsb@smart.net