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#11939: 24.1; `save-buffers-kill-emacs' loses minibuffer focus when itcalls `list-processes' Date: Mon, 23 Jul 2012 11:34:28 +0200 Message-ID: <500D1AA4.1080301@gmx.at> References: <500173A5.3040608@gmx.at><1986D90E22154321A44B6E0110CA4F5A@us.oracle.com><50019C2F.8060103@gmx.at><6B9036DBFDEF4881AB39804520BF63B3@us.oracle.com><5002BEC6.3040106@gmx.at><893E59C2E4F94D6EB910560C9E8C42CD@us.oracle.com><5002EAF4.5080107@gmx.at><6F73D04E8EE144E780D602DFEBA48E7B@us.oracle.com><5003DAF2.2060400@gmx.at><50043C3D.7090201@gmx.at><208B7D7BB4BC4339ADCC1166F76C1CD2@us.oracle.com><500449B7.6070309@gmx.at> <023F63BCBF9442EBAEDCCE9D8A59E5E4@us.oracle.com> <50053558.4040808@gmx.at> <28CDFF761F104E109F9F24CD9BEBD8DD@us.oracle.com> <5006E151.5080301@gmx.at> <1888F8FFBF624D39920F56673A91C4B6@us.oracle.com> <5007E482.3030401@gmx.at> <500A8C2D.8040005@gmx.at> <2F2A096477C74296B873241B8AD78AF5@us.oracle.com> <500BBE9B.3080006@gmx.at> NNTP-Posting-Host: plane.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 1343036082 350 80.91.229.3 (23 Jul 2012 09:34:42 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 23 Jul 2012 09:34:42 +0000 (UTC) Cc: 11939@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Jul 23 11:34:39 2012 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1StF2E-0008AM-PZ for geb-bug-gnu-emacs@m.gmane.org; Mon, 23 Jul 2012 11:34:39 +0200 Original-Received: from localhost ([::1]:52996 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1StF2D-0001nO-Mv for geb-bug-gnu-emacs@m.gmane.org; Mon, 23 Jul 2012 05:34:37 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:55919) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1StF28-0001aL-EQ for bug-gnu-emacs@gnu.org; Mon, 23 Jul 2012 05:34:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1StF25-0003Bn-Mz for bug-gnu-emacs@gnu.org; Mon, 23 Jul 2012 05:34:32 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:49426) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1StF25-0003Bj-Jj for bug-gnu-emacs@gnu.org; Mon, 23 Jul 2012 05:34:29 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1StF8Q-00049I-G2 for bug-gnu-emacs@gnu.org; Mon, 23 Jul 2012 05:41:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 23 Jul 2012 09:41:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 11939 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 11939-submit@debbugs.gnu.org id=B11939.134303644415918 (code B ref 11939); Mon, 23 Jul 2012 09:41:02 +0000 Original-Received: (at 11939) by debbugs.gnu.org; 23 Jul 2012 09:40:44 +0000 Original-Received: from localhost ([127.0.0.1]:58970 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1StF87-00048h-VA for submit@debbugs.gnu.org; Mon, 23 Jul 2012 05:40:44 -0400 Original-Received: from mailout-de.gmx.net ([213.165.64.23]:40125) by debbugs.gnu.org with smtp (Exim 4.72) (envelope-from ) id 1StF85-00048Z-7S for 11939@debbugs.gnu.org; Mon, 23 Jul 2012 05:40:42 -0400 Original-Received: (qmail invoked by alias); 23 Jul 2012 09:34:06 -0000 Original-Received: from 62-47-50-184.adsl.highway.telekom.at (EHLO [62.47.50.184]) [62.47.50.184] by mail.gmx.net (mp069) with SMTP; 23 Jul 2012 11:34:06 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX18eR/Q3RTYe13kzlnxmYLUoBMejRi1LmajLlY/ZAQ DsvCp8ORfLs6n4 In-Reply-To: X-Y-GMX-Trusted: 0 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) 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: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:62302 Archived-At: >> >> Usually, each frame must have a minibuffer window. How >> >> else should `read-minibuffer' work? >> > >> > It can read from the minibuffer in a standalone minibuffer frame? >> >> Is this a question or an answer? > > An answer, followed by "Is that not correct?", since I'm not sure we're talking > about the same thing. I would expect that it is obvious to you too that Emacs > can read from a minibuffer in a standalone frame. And it's not clear to me why > that possibility is not an answer to your question. But then you didn't answer my initial question. I didn't ask about standalone frames only, I asked about "each" frame. >> > That's what I was guessing, that a frame's `minibuffer' >> > parameter might be non-nil but it somehow has a minibuffer >> > _window_. Seems odd, but I guess these things are at two >> > different levels. I am used to the Lisp & frame level - I >> > know almost nothing about the C & window level. >> >> Emacs must be able to work internally even if you make all your frames >> minibuffer-less. > > I never claimed otherwise. But I don't see the relation here. And I do not > make all my frames minibuffer-less. So I guess I'm not following you very well. When you exit emacs deleting its last frame, there might be an internal state where only a minibuffer less frame remains. And that may cause a(n unwanted) crash IIUC. >> >> `mouse-leave-buffer-hook' and in a `pre-' or >> >> `post-command-hook' check whether that something got executed. >> >> Then you can be sure that somewhere in between a >> >> `handle-switch-frame' interfered. >> > >> > Sorry, I don't follow you (and I haven't found where you >> > suggested something similar earlier). If you can be more >> > specific I'll be glad to try whatever you ask. >> >> When you want to check of `handle-switch-frame' executions you cannot >> trace otherwise and you do not run emacs in the debugger, the most >> simple way to trace these is to put some function on >> `mouse-leave-buffer-hook', and inspect the output of that >> function later on. > > OK, but I still do not know what you would like me to do/test. Can you give me > a recipe to test? No. All I did was to reply to an issue you raised earlier - that of `handle-switch-frame' possibly interfering with "normal" execution of commands. And I said that IMHO the most simple way to notice whether `handle-switch-frame' got executed in between is to put a function on `mouse-leave-buffer-hook'. martin