From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Asynchronous DNS Date: Mon, 01 Feb 2016 03:46:36 +0100 Message-ID: <87d1shjgfn.fsf@gnus.org> References: <87si1gx6wz.fsf@gnus.org> <8360yby1gx.fsf@gnu.org> <87r3gzy0fb.fsf@gnus.org> <4D20ECD5-E3A0-4C17-97C2-EAC4C7CF6AD2@raeburn.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1454295303 24891 80.91.229.3 (1 Feb 2016 02:55:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 1 Feb 2016 02:55:03 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Ken Raeburn Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 01 03:54:53 2016 Return-path: Envelope-to: ged-emacs-devel@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 1aQ4df-0008Vu-O6 for ged-emacs-devel@m.gmane.org; Mon, 01 Feb 2016 03:54:51 +0100 Original-Received: from localhost ([::1]:44355 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aQ4df-0004Bu-BU for ged-emacs-devel@m.gmane.org; Sun, 31 Jan 2016 21:54:51 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49714) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aQ4WD-0000uP-7t for emacs-devel@gnu.org; Sun, 31 Jan 2016 21:47:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aQ4WA-0002Fj-1y for emacs-devel@gnu.org; Sun, 31 Jan 2016 21:47:09 -0500 Original-Received: from hermes.netfonds.no ([80.91.224.195]:42581) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aQ4W9-0002Ec-RV; Sun, 31 Jan 2016 21:47:05 -0500 Original-Received: from cpe-60-225-211-161.nsw.bigpond.net.au ([60.225.211.161] helo=mouse) by hermes.netfonds.no with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1aQ4Vl-0002t1-9F; Mon, 01 Feb 2016 03:46:41 +0100 In-Reply-To: <4D20ECD5-E3A0-4C17-97C2-EAC4C7CF6AD2@raeburn.org> (Ken Raeburn's message of "Sun, 31 Jan 2016 01:12:29 -0500") User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1.50 (gnu/linux) X-MailScanner-ID: 1aQ4Vl-0002t1-9F MailScanner-NULL-Check: 1454899602.43507@Y/O6bvszCNNNt7ANfwwB5A X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.224.195 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:199106 Archived-At: Ken Raeburn writes: > If I understand correctly, passing a name that can=92t be resolved, in > =93nowait=94 mode, used to raise an error but now will return a process > object that will report an error? Yes, that's true. So there is a user-visible difference here. But the documentation of make-network-process doesn't specify when that erroring is supposed to happen on :nowait, so anybody relying on that behaviour are doing something wrong... > If async resolving isn=92t enabled, which way will Emacs report a > failure to resolve? The same way as previously. --=20 (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no