From: Mike Kazantsev <mk.fraggod@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: npostavs@gmail.com, 31901@debbugs.gnu.org
Subject: bug#31901: Incorrect make-network-process + nowait state handling for non-existing unix sockets in emacs-26.1
Date: Sun, 22 Jul 2018 19:54:58 +0500 [thread overview]
Message-ID: <20180722195458.2e40086f@malediction> (raw)
In-Reply-To: <m3o9ezqz0c.fsf@gnus.org>
On Sun, 22 Jul 2018 13:40:51 +0200
Lars Ingebrigtsen <larsi@gnus.org> wrote:
> OK, I've now fixed the async error case (on master), I think:
>
> (process-live-p socket)
> nil
> (process-status socket)
> file-missing
>
> I've fixed this on master, because I'm not 100% sure that my fix is
> completely correct. Should we perhaps also call a sentinel in the async
> error case?
Unless I misunderstood the question, for me as a user, it would be more
obvious to get this error in a sentinel call than not with emacs 26,
because that's how :nowait is documented to work now:
The recommended way to deal with asynchronous sockets is to avoid
interacting with them until they have changed status to "run".
This is most easily done from a process sentinel.
https://github.com/emacs-mirror/emacs/blob/master/etc/NEWS.26
If bool is non-nil for a stream connection, return without waiting
for the connection to complete. When the connection succeeds or
fails, Emacs will call the sentinel function, with a second argument
matching "open" (if successful) or "failed".
https://www.gnu.org/software/emacs/manual/html_node/elisp/Network-Processes.html
Given either of these guidelines, it'd be more surprising to not get
error state in the sentinel call with ":nowait t" in emacs-26.
(while ":nowait nil" signaling 'file-error is kinda expected)
--
Mike Kazantsev // fraggod.net
next prev parent reply other threads:[~2018-07-22 14:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 5:43 bug#31901: Incorrect make-network-process + nowait state handling for non-existing unix sockets in emacs-26.1 Mike Kazantsev
2018-07-01 15:21 ` Noam Postavsky
2018-07-06 8:59 ` Eli Zaretskii
2018-07-14 8:20 ` Eli Zaretskii
2018-07-20 9:16 ` Eli Zaretskii
2018-07-20 10:08 ` Lars Ingebrigtsen
2018-07-20 12:17 ` Eli Zaretskii
2018-07-22 11:40 ` Lars Ingebrigtsen
2018-07-22 14:11 ` Eli Zaretskii
2018-07-22 14:31 ` Lars Ingebrigtsen
2018-07-22 14:54 ` Mike Kazantsev [this message]
2018-07-22 15:23 ` Lars Ingebrigtsen
2018-07-22 15:38 ` Mike Kazantsev
2018-07-22 15:56 ` Eli Zaretskii
2018-07-22 16:42 ` Mike Kazantsev
2018-07-22 16:55 ` Mike Kazantsev
2018-08-06 20:36 ` Noam Postavsky
2018-08-07 15:48 ` Eli Zaretskii
2018-08-08 23:51 ` Noam Postavsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180722195458.2e40086f@malediction \
--to=mk.fraggod@gmail.com \
--cc=31901@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).