From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Last change to process.c breaks fetching pop3 mail (gnus/pop3.el) Date: Wed, 02 Jun 2004 18:56:25 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20040530160908.436326.FMU25511@nutty-waffle-cone.splode.com> <20040531143416.431708.FMU25511@nutty-waffle-cone.splode.com> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1086217029 12887 80.91.224.253 (2 Jun 2004 22:57:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 2 Jun 2004 22:57:09 +0000 (UTC) Cc: friedman@splode.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Jun 03 00:57:01 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BVefN-0002H8-00 for ; Thu, 03 Jun 2004 00:57:01 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BVefM-0004lq-00 for ; Thu, 03 Jun 2004 00:57:01 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BVeff-00025J-Su for emacs-devel@quimby.gnus.org; Wed, 02 Jun 2004 18:57:19 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BVefB-0001sX-Vb for emacs-devel@gnu.org; Wed, 02 Jun 2004 18:56:50 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BVefA-0001rZ-BD for emacs-devel@gnu.org; Wed, 02 Jun 2004 18:56:48 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BVefA-0001rP-8X for emacs-devel@gnu.org; Wed, 02 Jun 2004 18:56:48 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BVeeo-0007Kp-FU for emacs-devel@gnu.org; Wed, 02 Jun 2004 18:56:26 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1BVeen-000057-Nn; Wed, 02 Jun 2004 18:56:25 -0400 Original-To: storm@cua.dk (Kim F. Storm) In-reply-to: (storm@cua.dk) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:24434 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24434 IIUC, the problem is that a network process' sentinel would like to be able to differentiate between the case where the connection is closed because the remote end closed the connection, or because it was closed by a call to delete-process. If that is the issue, we could arrange for delete-process to call the sentinel in a special way. Perhaps we could have a different state for connections closed by delete-process. Now, to let the sentinel treat network processes and subprocesses alike, Noah suggests that the sentinel could look to see if the process' buffer is still alive. That is clearly the wrong criterion, since after delete-process the buffer would often still be alive. The string passed to the sentinel is "finished\n" if delete-process was called; otherwise it is "exited abnormally with code 256". That general idea is ok, though using the status symbol would be a cleaner way to distinguish. But "finished" is the wrong way to decribe delete-process. "deleted" would be more appropriate.