From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#8184: 23.1.90; `menu-bar-non-minibuffer-window-p' error in callsto `kill-this-buffer' Date: Mon, 07 Mar 2011 09:07:48 +0100 Message-ID: <4D749254.4090009@gmx.at> References: <4D73D021.8070105@gmx.at> <4D73DCF0.9080604@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1299487030 5716 80.91.229.12 (7 Mar 2011 08:37:10 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 7 Mar 2011 08:37:10 +0000 (UTC) Cc: 8184@debbugs.gnu.org, 'tlh' To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Mar 07 09:37:05 2011 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PwVw9-0003dp-FK for geb-bug-gnu-emacs@m.gmane.org; Mon, 07 Mar 2011 09:37:05 +0100 Original-Received: from localhost ([127.0.0.1]:55800 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PwVw8-0002xC-RO for geb-bug-gnu-emacs@m.gmane.org; Mon, 07 Mar 2011 03:37:04 -0500 Original-Received: from [140.186.70.92] (port=44694 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PwVvx-0002wc-Sj for bug-gnu-emacs@gnu.org; Mon, 07 Mar 2011 03:36:55 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PwVvw-0005Lv-6O for bug-gnu-emacs@gnu.org; Mon, 07 Mar 2011 03:36:53 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:41394) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PwVvw-0005Lm-43 for bug-gnu-emacs@gnu.org; Mon, 07 Mar 2011 03:36:52 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1PwVU2-0004O8-Cx; Mon, 07 Mar 2011 03:08:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 07 Mar 2011 08:08:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 8184 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 8184-submit@debbugs.gnu.org id=B8184.129948527916853 (code B ref 8184); Mon, 07 Mar 2011 08:08:02 +0000 Original-Received: (at 8184) by debbugs.gnu.org; 7 Mar 2011 08:07:59 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1PwVTy-0004Nj-Hb for submit@debbugs.gnu.org; Mon, 07 Mar 2011 03:07:59 -0500 Original-Received: from mailout-de.gmx.net ([213.165.64.23]) by debbugs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1PwVTw-0004NN-D8 for 8184@debbugs.gnu.org; Mon, 07 Mar 2011 03:07:57 -0500 Original-Received: (qmail invoked by alias); 07 Mar 2011 08:07:50 -0000 Original-Received: from 62-47-40-198.adsl.highway.telekom.at (EHLO [62.47.40.198]) [62.47.40.198] by mail.gmx.net (mp031) with SMTP; 07 Mar 2011 09:07:50 +0100 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1/kfcw7rcbkeUQ51i8zSGqtulzwAeSkGubXAJsl9G ENUSGIg/I+FSb3 User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: X-Y-GMX-Trusted: 0 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Mon, 07 Mar 2011 03:08:02 -0500 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:44736 Archived-At: >> The idea is that at least _two_ interesting buffers are >> needed to enable `kill-this-buffer'. > > Right, that's the existing behavior. > > But why? Why shouldn't menu item `Close' be available to kill the current > buffer even if it is the only "interesting" buffer? I imagine the answer behind > this design is that we never want to show an uninteresting buffer - or that we > never want to replace an interesting one by an uninteresting one in the same > window. We might end up showing the *code-conversion-work* or *Echo Area* buffer in a normal window which doesn't strike me as a good idea in response to invoking a menu item called "Close". > I don't think that's a good idea. (I mistakenly thought you were trying to > improve this at the same time as improving the performance - see below.) > > `Close' is about killing the buffer. It is not just or even primarily about > replacing it with another in the window. I'd say we should let the user kill > the buffer even if it is the only "interesting" one. A user will wonder (bad > UI) why `Close' isn't available in this case, and even if s?he correctly guesses > why s?he won't necessarily care that there is no other non-interesting buffer to > display. We should not prevent the user from killing the buffer (via the menu). I only tried to emulate the current behavior. Usually, at least the *scratch* or *Messages* buffer should be around so I suppose that in practice it's always possible to kill the current buffer. martin