From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Lennart Borgman (gmail)" Newsgroups: gmane.emacs.devel Subject: Re: Emacs does not listen on w32 Date: Sun, 13 Apr 2008 17:19:57 +0200 Message-ID: <4802249D.2060909@gmail.com> References: <4800D965.9080202@gmail.com> <480208C8.3030401@gnu.org> <480212F7.7090409@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1208100034 31073 80.91.229.12 (13 Apr 2008 15:20:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 13 Apr 2008 15:20:34 +0000 (UTC) Cc: Emacs Devel , Stefan Monnier , Jason Rumney To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 13 17:21:09 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Jl40k-0002MH-S2 for ged-emacs-devel@m.gmane.org; Sun, 13 Apr 2008 17:20:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jl406-0007Qu-Nu for ged-emacs-devel@m.gmane.org; Sun, 13 Apr 2008 11:20:14 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jl402-0007QL-JH for emacs-devel@gnu.org; Sun, 13 Apr 2008 11:20:10 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jl401-0007O0-1t for emacs-devel@gnu.org; Sun, 13 Apr 2008 11:20:10 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jl400-0007Nm-PW for emacs-devel@gnu.org; Sun, 13 Apr 2008 11:20:08 -0400 Original-Received: from ch-smtp01.sth.basefarm.net ([80.76.149.212]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jl3zw-00083x-4X; Sun, 13 Apr 2008 11:20:04 -0400 Original-Received: from c83-254-150-27.bredband.comhem.se ([83.254.150.27]:62759 helo=[127.0.0.1]) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1Jl3zt-000243-5T; Sun, 13 Apr 2008 17:20:02 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 In-Reply-To: X-Antivirus: avast! (VPS 080413-0, 2008-04-13), Outbound message X-Antivirus-Status: Clean X-Originating-IP: 83.254.150.27 X-Scan-Result: No virus found in message 1Jl3zt-000243-5T. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1Jl3zt-000243-5T 4e8bc2325954a73bcb3420a4bee9fbfb X-detected-kernel: by monty-python.gnu.org: Linux 2.6? (barebone, rare!) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:95107 Archived-At: Juanma Barranquero wrote: > On Sun, Apr 13, 2008 at 4:04 PM, Lennart Borgman (gmail) > wrote: > >> I would expect that the message sent to the Emacs when clicking on the >> upper left [X] would terminate any loop, just like C-g terminates a loop in >> a command. > > keyboard-quit's function is to signal a `quit' condition, so it does it. > > Clicking the upper left [X] sends a WM_CLOSE message to Emacs, which > tells it to do an orderly exit. That includes executing Lisp code, and > potentially doing a lot of things: writing files, asking the user, > killing subprocesses, etc. If some of these things take forever, how > it is Emacs to know that it is a bug and not expected behavior? For > example, if something in kill-emacs-query-functions asks me and I > don't answer, I wouldn't want Emacs to assume it can proceed... Yes, those are good points, but I think you are perhaps missing my point: That WM_CLOSE should be treated more like qiut. That does not prevent Emacs from asking the type of question you mentioned.