From: Aaron Meurer <asmeurer@gmail.com>
To: BDB <noemail@yahoo.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Hide extraneous buffers?
Date: Fri, 18 May 2012 16:54:46 -0600 [thread overview]
Message-ID: <CAKgW=6+m60wkit12piZDYHwxM9rXo-dy1kpkz6D0hg4hvurWkQ@mail.gmail.com> (raw)
In-Reply-To: <slrnjrdcms.37m.noemail@us.news.astraweb.com>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
There are literally dozens of packages that manage buffers. If you Google
around, you're sure to find one that fits your needs. It sounds like you
just want to create a custom next-buffer that skips those buffers you don't
want.
Aaron Meurer
On Friday, May 18, 2012, BDB wrote:
> Mark Skilbeck wrote:
> > How exactly are you cycling through the buffers? If you know the names of
> > the buffers, simply using C-x b with a partial-string can complete the
> buffer
> > name for you. If you don't know the names of the buffers you're
> interested in,
> > you're still going ot require casting an eye on the buffer list. Really,
> > what's 3 extra buffer names?
>
> I like to use next-buffer bound to a key to cycle through the open buffers.
> I googled around and found buffer-stack.el, which kind of minimizes the
> problem by keeping the less recently used buffers at the bottom of the
> stack,
> however it's still annoying to have the clutter around. It's actually
> pretty
> surprising nobody has made a fix for this.
>
> > P.S. If you're not, you should probably be using IDO[1].
>
> Thanks, but I'm not looking to change my behavior to fit emacs, but the
> other way around :)
>
--
Sent from my iPad.
[-- Attachment #2: Type: text/html, Size: 1493 bytes --]
next prev parent reply other threads:[~2012-05-18 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1361.1337366454.855.help-gnu-emacs@gnu.org>
2012-05-18 20:36 ` Hide extraneous buffers? BDB
2012-05-18 22:54 ` Aaron Meurer [this message]
2012-05-18 18:40 Mark Skilbeck
-- strict thread matches above, loose matches on Subject: below --
2012-05-18 18:03 BDB
2012-05-18 18:38 ` Mark Skilbeck
2012-05-18 20:39 ` Drew Adams
2012-05-19 0:18 ` Xah Lee
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='CAKgW=6+m60wkit12piZDYHwxM9rXo-dy1kpkz6D0hg4hvurWkQ@mail.gmail.com' \
--to=asmeurer@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=noemail@yahoo.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.
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).