unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: John Paul Wallington <jpw@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: ibuffer: hard to keep hidden buffers unhidden
Date: Fri, 15 Oct 2004 08:44:05 +0100	[thread overview]
Message-ID: <86k6tsctoa.fsf@vaio.shootybangbang.com> (raw)
In-Reply-To: <87acupgdit.fsf@jidanni.org> (message from Dan Jacobson on Fri, 15 Oct 2004 06:07:06 +0800)

> It's real hard to keep hidden buffers (names matching
> ibuffer-maybe-show-regexps /^ /) shown in ibuffer.  You must use 0g to
> see them. Any subsequent g (ibuffer-update) or ibuffer-and-update or
> ibuffer calls will wipe them out.
> 
> No one doesn't want to see them every day, but when one does have them
> visible, ibuffer should be like dired, which respects your ls flags
> across revert-buffer (g) invocations.

In the current sources it's `ibuffer-maybe-show-predicates' and C-u g
to display buffers that match.

I'm not sure the current behaviour is a total misfeature because I
like to break out of displaying buffers matching
`ibuffer-maybe-show-predicates' without killing the Ibuffer buffer and
reinvoking `ibuffer'.  However, I agree that it would also be nice for
Ibuffer to behave as you expect.

How about making C-u g toggle whether it and subsequent invocations of
g should display buffers matching `ibuffer-maybe-show-predicates' ?
WDYT?

      reply	other threads:[~2004-10-15  7:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 22:07 ibuffer: hard to keep hidden buffers unhidden Dan Jacobson
2004-10-15  7:44 ` John Paul Wallington [this message]

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=86k6tsctoa.fsf@vaio.shootybangbang.com \
    --to=jpw@gnu.org \
    --cc=bug-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.
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).