unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 69987-done@debbugs.gnu.org, tom@logand.com, juri@linkov.net
Subject: bug#69987: 28.2; *mailcap shell* not in buffer list
Date: Mon, 25 Mar 2024 14:55:12 +0200	[thread overview]
Message-ID: <86msqmjwsv.fsf@gnu.org> (raw)
In-Reply-To: <87wmpqbtik.fsf@gmx.net> (message from Stephen Berman on Mon, 25 Mar 2024 09:33:23 +0100)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: Tomas Hlavaty <tom@logand.com>,  69987@debbugs.gnu.org,  Eli Zaretskii
>  <eliz@gnu.org>
> Date: Mon, 25 Mar 2024 09:33:23 +0100
> 
> On Mon, 25 Mar 2024 09:55:37 +0200 Juri Linkov <juri@linkov.net> wrote:
> 
> >> then C-x C-b to show *Buffer List*
> >
> > In the *Buffer List* you can see all internal buffers
> > by typing 'I' (Buffer-menu-toggle-internal).
> 
> Does the "---" line above the NEWS entry for this feature mean the "List
> Buffers" node in the Emacs manual will be updated to mention it?

No, it means we didn't think this worth documenting.  Now reconsidered.

I'm therefore closing this bug.





  reply	other threads:[~2024-03-25 12:55 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
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 [this message]
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=86msqmjwsv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69987-done@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --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).