From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: z@bcc32.com, 71295@debbugs.gnu.org, azeng@janestreet.com
Subject: bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs
Date: Fri, 07 Jun 2024 09:20:11 +0300 [thread overview]
Message-ID: <86sexpff50.fsf@gnu.org> (raw)
In-Reply-To: <f0bbb42a-2bc9-40ec-9054-4fad81828db6@gutov.dev> (message from Dmitry Gutov on Thu, 6 Jun 2024 23:41:39 +0300)
> Date: Thu, 6 Jun 2024 23:41:39 +0300
> Cc: 71295@debbugs.gnu.org, azeng@janestreet.com
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> On 06/06/2024 14:40, Eli Zaretskii wrote:
> >> This is probably rather naive of me, but I guess now I'm wondering why url-retrieve-synchronously actually sets url-asynchronous to nil. Is there a good reason not to use :nowait when it is available? It seems like it would be useful to have a wrapper around url-retrieve that just "does what I mean" here.
> > Maybe. I wonder what others think about this.
>
> It seems like a leaky abstraction (the caller has to be aware that what
> happens under the covers is done in several steps, and the timeout only
> applies to subsequent ones).
>
> If we could change the implementation to a more intuitive behavior, that
> would be a win, I think. Can somebody think of adverse effects?
Do you have a patch to consider?
next prev parent reply other threads:[~2024-06-07 6:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 16:21 bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs Aaron Zeng
2024-06-01 19:38 ` Eli Zaretskii
2024-06-04 0:09 ` Aaron Zeng
2024-06-06 11:40 ` Eli Zaretskii
2024-06-06 20:41 ` Dmitry Gutov
2024-06-07 6:20 ` Eli Zaretskii [this message]
2024-06-07 21:32 ` Dmitry Gutov
2024-06-08 6:08 ` Eli Zaretskii
2024-06-08 22:34 ` Dmitry Gutov
2024-06-09 4:39 ` Eli Zaretskii
2024-06-09 22:05 ` Dmitry Gutov
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=86sexpff50.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71295@debbugs.gnu.org \
--cc=azeng@janestreet.com \
--cc=dmitry@gutov.dev \
--cc=z@bcc32.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).