From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: Emacs does not listen on w32 Date: Sun, 13 Apr 2008 16:16:31 +0200 Message-ID: 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 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1208096202 17593 80.91.229.12 (13 Apr 2008 14:16:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 13 Apr 2008 14:16:42 +0000 (UTC) Cc: Emacs Devel , Stefan Monnier , Jason Rumney To: "Lennart Borgman (gmail)" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 13 16:17:20 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 1Jl31D-0000cQ-Nk for ged-emacs-devel@m.gmane.org; Sun, 13 Apr 2008 16:17:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jl30Z-0003bK-HK for ged-emacs-devel@m.gmane.org; Sun, 13 Apr 2008 10:16:39 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jl30U-0003Zt-Tq for emacs-devel@gnu.org; Sun, 13 Apr 2008 10:16:34 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jl30T-0003YB-Da for emacs-devel@gnu.org; Sun, 13 Apr 2008 10:16:34 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jl30T-0003Y8-83 for emacs-devel@gnu.org; Sun, 13 Apr 2008 10:16:33 -0400 Original-Received: from wa-out-1112.google.com ([209.85.146.183]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jl30T-0003Jx-5R for emacs-devel@gnu.org; Sun, 13 Apr 2008 10:16:33 -0400 Original-Received: by wa-out-1112.google.com with SMTP id k34so1461354wah.10 for ; Sun, 13 Apr 2008 07:16:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=9qU2+Fk2B0A8gAjQ+RfpSErllf1M21muocQr5H7i41A=; b=JLtuHizen1v69fm5LBKQ+rt+w09bgLJVqSwW4/xUA5XfdKL8uJgxn/voRuvl47YVUQ9fzDoQIPfs8p7l94pt/H57GYcZb7gc8sG7SZSPIgNCvNBd1hwnpzsP+x/Xtn2DNCE9gXPAJLArR60ZpdhcA720aQ4B1bTK5dPBk2p2+w4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mEwCDpLmaFvzMTVUrGp6rW1iKrS56/B1hxmK4bpVrIkF2KxnQpCj7lVWVcmEmopUWR6kj34DksR+jZwLSB/TkVzg0RW2hrCNLkuifwi+RSvaR4SiRLi5yn7SszcGrGX6wTnFLcI792q1alDuD2uw82TIT8Jx5wbXsNRyoWSaF2Q= Original-Received: by 10.114.144.1 with SMTP id r1mr5761302wad.135.1208096191337; Sun, 13 Apr 2008 07:16:31 -0700 (PDT) Original-Received: by 10.115.72.13 with HTTP; Sun, 13 Apr 2008 07:16:31 -0700 (PDT) In-Reply-To: <480212F7.7090409@gmail.com> Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) 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:95104 Archived-At: 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... Juanma