unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: 2QdxY4RzWzUUiLuE@potatochowder.com
To: help-gnu-emacs@gnu.org
Subject: Re: url-retrieve fails on most HTTPS sites
Date: Tue, 29 Sep 2020 06:29:04 -0500	[thread overview]
Message-ID: <20200929112904.GD128690@scrozzle> (raw)
In-Reply-To: <87eemldtkd.fsf@yandex.com>

On 2020-09-29 at 06:45:54 +0100,
Colin Baxter <m43cap@yandex.com> wrote:

> >>>>> 2QdxY4RzWzUUiLuE  <2QdxY4RzWzUUiLuE@potatochowder.com> writes:
> 
> ----- Cut -----
> 
>     > 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.
> 
> Yes, that works for me too. Strange. I wonder why the buffer doesn't appear
> elsewhere, e.g. when Ibuffer is run?

As per the manual¹:

    Buffers that are ephemeral and generally uninteresting to the user
    have names starting with a space, so that the list-buffers and
    buffer-menu commands don’t mention them (but if such a buffer visits
    a file, it is mentioned). A name starting with space also initially
    disables recording undo information; see Undo.

¹ https://www.gnu.org/software/emacs/manual/html_node/elisp/Buffer-Names.html



  reply	other threads:[~2020-09-29 11:29 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
2020-09-29  5:45         ` Colin Baxter
2020-09-29 11:29           ` 2QdxY4RzWzUUiLuE [this message]
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=20200929112904.GD128690@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).