From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Moreton Newsgroups: gmane.emacs.devel Subject: Re: Uhm... weird frame behaviour Date: Mon, 12 Sep 2011 14:32:57 +0100 Message-ID: References: <4E6C80BF.2060002@gmx.at> <4E6DCB0A.4060605@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1315834400 11154 80.91.229.12 (12 Sep 2011 13:33:20 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 12 Sep 2011 13:33:20 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 12 15:33: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 1R36dQ-0005pT-LA for ged-emacs-devel@m.gmane.org; Mon, 12 Sep 2011 15:33:16 +0200 Original-Received: from localhost ([::1]:47651 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R36dQ-00065J-4f for ged-emacs-devel@m.gmane.org; Mon, 12 Sep 2011 09:33:16 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:46671) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R36dM-00064s-Sa for emacs-devel@gnu.org; Mon, 12 Sep 2011 09:33:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R36dL-0005oZ-LP for emacs-devel@gnu.org; Mon, 12 Sep 2011 09:33:12 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:44608) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R36dL-0005oH-Ci for emacs-devel@gnu.org; Mon, 12 Sep 2011 09:33:11 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R36dJ-0005nR-Ml for emacs-devel@gnu.org; Mon, 12 Sep 2011 15:33:09 +0200 Original-Received: from 193.34.186.16 ([193.34.186.16]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Sep 2011 15:33:09 +0200 Original-Received: from andrewjmoreton by 193.34.186.16 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Sep 2011 15:33:09 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 36 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 193.34.186.16 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (windows-nt) Cancel-Lock: sha1:S+YqliH+DeNDZfLYwvC9Ihu+078= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 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:143931 Archived-At: On Mon 12 Sep 2011, martin rudalics wrote: >>> Which function does `q' run? >> >> `gnus-group-quit'. > > Which ends up calling `kill-buffer'? > >>>> Can this be explained by any of the recent window code shenanigans? >>> It's probably because the frame in question didn't show another buffer >>> before. Which buffer did you expect it to show after typing `q'? >> >> Any random buffer. > > So you wanted to show a random buffer as placeholder. A buffer you > didn't intend to view or edit. I think Lars would like the previous behaviour, where some buffer is chosen for display (which buffer is not important). I'd like this fixed too, as frames being randomly deleted is disconcerting to say the least. >> Killing a buffer has never deleted a frame before. > > See the thread on bug#9419 for an explanation and how to > disable the behavior. Emacs previously did not delete frames is this way, so it is a regression and thus a bug to be fixed. If configuration is required to fix this behaviour, then the default setting is wrong and needs to be changed. AndyM