[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial
From: |
Eli Zaretskii |
Subject: |
bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs |
Date: |
Thu, 06 Jun 2024 14:40:05 +0300 |
> Date: Mon, 03 Jun 2024 20:09:03 -0400
> From: "Aaron Zeng" <z@bcc32.com>
> Cc: 71295@debbugs.gnu.org, azeng@janestreet.com
>
> Is the idea just to use url-retrieve directly?
I think so, yes.
> 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.
- bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs, Eli Zaretskii, 2024/06/01
- bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs, Aaron Zeng, 2024/06/03
- bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs,
Eli Zaretskii <=
- bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs, Dmitry Gutov, 2024/06/06
- bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs, Eli Zaretskii, 2024/06/07
- bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs, Dmitry Gutov, 2024/06/07
- bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs, Eli Zaretskii, 2024/06/08
- bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs, Dmitry Gutov, 2024/06/08
- bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs, Eli Zaretskii, 2024/06/09
- bug#71295: 29.3; url-retrieve-synchronously does not timeout if initial connection hangs, Dmitry Gutov, 2024/06/09