unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Brett Gilio <brettg@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: `url-insert-file-contents' not reliably connecting.
Date: Wed, 19 Aug 2020 22:49:41 -0500	[thread overview]
Message-ID: <87blj6m0x6.fsf@gnu.org> (raw)
In-Reply-To: <87mu2qdqe2.fsf@gnu.org> (Brett Gilio's message of "Wed, 19 Aug 2020 21:04:21 -0500")

Brett Gilio <brettg@gnu.org> writes:

> When given this variable set, with 6 entries. There are times where it
> will connect to 5, 6, 4, 2, 3... and terminate successfully without
> producing any error message. There is not any suspected connectivity
> issue, as when that occurs an error message DOES get raised. It just
> seems to terminate whenever it thinks it is done, but never
> consistently, and never in the same order.

Update, This behavior is consistent across both 26.3 and 27.1.

Brett Gilio



  reply	other threads:[~2020-08-20  3:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20  2:04 `url-insert-file-contents' not reliably connecting Brett Gilio
2020-08-20  3:49 ` Brett Gilio [this message]
2020-08-20  6:14   ` Brett Gilio

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=87blj6m0x6.fsf@gnu.org \
    --to=brettg@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).