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: Uhm... weird frame behaviour Date: Mon, 12 Sep 2011 11:04:10 +0200 Message-ID: <4E6DCB0A.4060605@gmx.at> References: <4E6C80BF.2060002@gmx.at> 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 1315818276 26267 80.91.229.12 (12 Sep 2011 09:04:36 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 12 Sep 2011 09:04:36 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lars Magne Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 12 11:04:28 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 1R32RI-0007yN-4x for ged-emacs-devel@m.gmane.org; Mon, 12 Sep 2011 11:04:28 +0200 Original-Received: from localhost ([::1]:53894 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R32RH-0001Ui-Hv for ged-emacs-devel@m.gmane.org; Mon, 12 Sep 2011 05:04:27 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:53694) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R32RA-0001UI-FB for emacs-devel@gnu.org; Mon, 12 Sep 2011 05:04:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R32R3-0002xn-AD for emacs-devel@gnu.org; Mon, 12 Sep 2011 05:04:20 -0400 Original-Received: from mailout-de.gmx.net ([213.165.64.22]:35878) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1R32R2-0002xQ-UY for emacs-devel@gnu.org; Mon, 12 Sep 2011 05:04:13 -0400 Original-Received: (qmail invoked by alias); 12 Sep 2011 09:04:11 -0000 Original-Received: from 62-47-59-1.adsl.highway.telekom.at (EHLO [62.47.59.1]) [62.47.59.1] by mail.gmx.net (mp050) with SMTP; 12 Sep 2011 11:04:11 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX18f+OdhpsofYOuH4CT38T1eOyx44Vh0ofD2lw1lsQ 5r02/PtQ/e9b12 User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: 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.22 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:143922 Archived-At: >> 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. > Killing a buffer has never deleted a frame before. See the thread on bug#9419 for an explanation and how to disable the behavior. martin