unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: 24962@debbugs.gnu.org
Subject: bug#24962: 26.0.50; list-buffers doesn't show buffers w/ name " "... visiting a file
Date: Fri, 18 Nov 2016 19:09:44 +0200	[thread overview]
Message-ID: <831sy8d89z.fsf@gnu.org> (raw)
In-Reply-To: <5b913ac1-94ef-c0c1-765a-f39bed313840@gmail.com> (message from Clément Pit--Claudel on Fri, 18 Nov 2016 11:48:07 -0500)

> From: Clément Pit--Claudel <clement.pit@gmail.com>
> Date: Fri, 18 Nov 2016 11:48:07 -0500
> 
> >> >From the Emacs manual:
> >> doc/lispref/buffers.texi (Buffer Names):
> >> Buffers that are ephemeral and generally uninteresting to the user
> >> have names starting with a space, so that the @code{list-buffers} and
> >> @code{buffer-menu} commands don't mention them (but if such a buffer
> >> visits a file, it @strong{is} mentioned).
> > 
> > Thank.  Please add a test for this to the test suite.
> 
> Could we fix the manual instead? Or do we have evidence that all modes that use temporary buffers visiting files set buffer-file-name to nil to prevent these buffers from being listed?

I'm not sure what use case you have in mind.  Usually, temporary
buffers don't visit files, those files are inserted into temporary
buffers without affecting buffer-file-name.  But maybe you are talking
about some scenario I'm missing.





  reply	other threads:[~2016-11-18 17:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 11:15 bug#24962: 26.0.50; list-buffers doesn't show buffers w/ name " "... visiting a file Tino Calancha
2016-11-18 12:41 ` Tino Calancha
2016-11-18 14:31 ` Eli Zaretskii
2016-11-18 16:48   ` Clément Pit--Claudel
2016-11-18 17:09     ` Eli Zaretskii [this message]
2016-11-30  3:22       ` Clément Pit--Claudel
2016-11-30  2:59     ` Tino Calancha
2016-12-08  4:54   ` Tino Calancha

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=831sy8d89z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24962@debbugs.gnu.org \
    --cc=clement.pit@gmail.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).