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 23:09:21 +0200 Message-ID: References: <4800D965.9080202@gmail.com> <480208C8.3030401@gnu.org> <480212F7.7090409@gmail.com> <4802249D.2060909@gmail.com> <480271D2.7040304@gmail.com> <4802756C.6000005@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 1208121011 30116 80.91.229.12 (13 Apr 2008 21:10:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 13 Apr 2008 21:10:11 +0000 (UTC) Cc: Eli Zaretskii , jasonr@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: "Lennart Borgman (gmail)" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 13 23:10:47 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 1Jl9TA-000594-UN for ged-emacs-devel@m.gmane.org; Sun, 13 Apr 2008 23:10:37 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jl9SW-0000lQ-MA for ged-emacs-devel@m.gmane.org; Sun, 13 Apr 2008 17:09:56 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jl9S3-0000g3-0R for emacs-devel@gnu.org; Sun, 13 Apr 2008 17:09:27 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jl9Rz-0000en-9o for emacs-devel@gnu.org; Sun, 13 Apr 2008 17:09:26 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jl9Rz-0000ei-4u for emacs-devel@gnu.org; Sun, 13 Apr 2008 17:09:23 -0400 Original-Received: from wa-out-1112.google.com ([209.85.146.181]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jl9Rz-0005De-2D for emacs-devel@gnu.org; Sun, 13 Apr 2008 17:09:23 -0400 Original-Received: by wa-out-1112.google.com with SMTP id k34so1644581wah.10 for ; Sun, 13 Apr 2008 14:09:22 -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=zc1+WDGvYW8if+jMOe4neY+34N97QaDC/J1VV5Q0fbI=; b=Gri9JwCKyn1gdlre25FMvizJwpJacdXxj7F3WA9Wq78MTU/mTruIASmacUf3cG+4qVMJoz3HNoRTZg6/8KrlPyWMkwOzEOIboktL/jgBwkCu1u6X8oYakrABn8RZc/Kr9/jkeEwbv8ZKBxoV5bm9tyOk0vTeyh873vV4EXkH6lQ= 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=V5tLr+UpClvphzzIfhQbC9uYoy57ivpsiW5Ixy5kcZ7Slcuic9iGE7EXL6g50PYiqeWIi1FrRxGM82xSM7DlQ0JOrzBA0fi6zfGkRD2+7JxMpa623ydgZmzScS8aiZ0I8l66f2BQGdJ3eJBA533ABWLzi00pbaDeF/eStbjxXUI= Original-Received: by 10.115.79.1 with SMTP id g1mr6101582wal.2.1208120961721; Sun, 13 Apr 2008 14:09:21 -0700 (PDT) Original-Received: by 10.115.72.13 with HTTP; Sun, 13 Apr 2008 14:09:21 -0700 (PDT) In-Reply-To: <4802756C.6000005@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:95128 Archived-At: On Sun, Apr 13, 2008 at 11:04 PM, Lennart Borgman (gmail) wrote: > By recognizing that it has recieved WM_CLOSE. I tried to say that this > should be handled as a kind of "quit" in those cases. Why should clicking into the [X] box interrupt useful work without asking? What will you do if some code in one of `kill-emacs-hook' or `kill-emacs-query-functions' loops forever? (They would run *after* your "quitting behavior" was done, IIUC what you're saying.) Juanma