unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Tomas Hlavaty <tom@logand.com>
Cc: 69987@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#69987: 28.2; *mailcap shell* not in buffer list
Date: Mon, 25 Mar 2024 00:25:25 +0100	[thread overview]
Message-ID: <87r0fzqkka.fsf@gmx.net> (raw)
In-Reply-To: <87zfunp8r5.fsf@neko.mail-host-address-is-not-set> (Tomas Hlavaty's message of "Sun, 24 Mar 2024 23:25:50 +0100")

On Sun, 24 Mar 2024 23:25:50 +0100 Tomas Hlavaty <tom@logand.com> wrote:

> Hi Eli,
>
> thanks for the quick reply.
>
>> Can you show a recipe, preferably starting from "emacs -Q"?  Or at
>> least explain how you get to this *mailcap shell* buffer?
>
> $ emacs -Q --eval='(eww
> "https://dq4n3btxmr8c9.cloudfront.net/files/oj7hht/Liberties_Rule_Of_Law_Report_2024_FULL.pdf")'
>
> then C-x 1 to hide the *mailcal shell* buffer
>
> then C-x C-b to show *Buffer List*
>
>> A stab in the dark: if the buffer's name is actually " *mailcap shell*",
>> i.e. it begins with a space,
>
> you are right, fascinating
>
>> then you can switch to it by typing its name at the "C-x b" prompt.
>
> this works, thank you!
>
> although not very discoverable
>
> Where could I learn more about such buffer name conventions?

In the Emacs user's manual (info "(emacs) List Buffers"):

   21.2 Listing Existing Buffers
   =============================
   
   ‘C-x C-b’
        List the existing buffers (‘list-buffers’).
   [...]
      ‘list-buffers’ omits buffers whose names begin with a space, unless
   they visit files: such buffers are used internally by Emacs.

With `M-x ibuffer' you get a table of all buffers, including those
beginning with a space, by typing `C-u g' in the *Ibuffer* buffer.

Steve Berman





  reply	other threads:[~2024-03-24 23:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-24 19:12 bug#69987: 28.2; *mailcap shell* not in buffer list tom
2024-03-24 19:32 ` Eli Zaretskii
2024-03-24 22:25   ` Tomas Hlavaty
2024-03-24 23:25     ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-03-25  6:20       ` Tomas Hlavaty
2024-03-25  7:55     ` Juri Linkov
2024-03-25  8:33       ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-25 12:55         ` Eli Zaretskii
2024-03-25 13:11           ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87r0fzqkka.fsf@gmx.net \
    --to=bug-gnu-emacs@gnu.org \
    --cc=69987@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stephen.berman@gmx.net \
    --cc=tom@logand.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).