From: 2QdxY4RzWzUUiLuE@potatochowder.com
To: help-gnu-emacs@gnu.org
Subject: Re: url-retrieve fails on most HTTPS sites
Date: Mon, 28 Sep 2020 21:50:54 -0500 [thread overview]
Message-ID: <20200929025054.GC128690@scrozzle> (raw)
In-Reply-To: <87blhpsc4b.fsf@ebih.ebihd>
On 2020-09-29 at 01:41:24 +0200,
Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> Re: url-retrieve fails on most HTTPS sites
> 2QdxY4RzWzUUiLuE wrote:
>
> > On 2020-09-29 at 01:13:51 +0200,
> > Emanuel Berg via Users list for the GNU Emacs text
> > editor <help-gnu-emacs@gnu.org> wrote:
> >
> >> Nicolas Graner wrote:
> >>
> >> > (switch-to-buffer (url-retrieve
> >> > "https://wikipedia.org/" '(lambda (&rest ignore))))
> >> >
> >> > The buffer that shows up is empty.
> >>
> >> Never heard of `url-retrieve' but I have it and yes,
> >> what "shows up is empty".
> >
> > It works for me. Sort of.
> >
> > I ran (url-retrieve "https://wikipedia.org/"
> > (lambda (&rest ignore))) in my *scratch* buffer,
> > and watched carefully.
> >
> (url-retrieve
> "https://wikipedia.org/"
> (lambda (&rest ignore)))
> #<buffer *http wikipedia.org:443*>
>
> I search downwards for some sign, signals aren't
> strong enough, perhaps?
At first, I could have sworn that url-retrieve inserted the name of a
second buffer in my *scratch* buffer, but I can't reproduce that now.
It all happened so fast the first time, so maybe it was just my
imagination.
In any case, I ran switch-to-buffer and then pressed the space bar and
the TAB key to display all the buffers whose names began with a space,
and one of those buffers was " *http www.wikipedia.org:443*," and that's
how I found it.
next prev parent reply other threads:[~2020-09-29 2:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 20:41 url-retrieve fails on most HTTPS sites Nicolas Graner
2020-09-28 23:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-28 23:24 ` 2QdxY4RzWzUUiLuE
2020-09-28 23:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 2:26 ` Stefan Monnier
2020-09-29 3:24 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 9:31 ` tomas
2020-09-29 9:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 10:32 ` tomas
2020-09-29 10:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 14:14 ` Sharp--quote [was: url-retrieve fails on most HTTPS sites] tomas
2020-09-29 14:56 ` Stefan Monnier
2020-09-29 15:19 ` tomas
2020-09-29 16:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 16:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 15:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 3:45 ` url-retrieve fails on most HTTPS sites 황병희
2020-09-29 2:50 ` 2QdxY4RzWzUUiLuE [this message]
2020-09-29 5:45 ` Colin Baxter
2020-09-29 11:29 ` 2QdxY4RzWzUUiLuE
2020-09-29 13:57 ` Colin Baxter
2020-09-29 14:53 ` HTTPS fails (was: url-retrieve fails on most HTTPS sites) Nicolas Graner
2020-09-29 15:10 ` Nicolas Graner
2020-09-29 15:16 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-29 14:47 ` url-retrieve fails on most HTTPS sites Noam Postavsky
2020-09-29 15:08 ` Nicolas Graner
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=20200929025054.GC128690@scrozzle \
--to=2qdxy4rzwzuuilue@potatochowder.com \
--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).