From: Daniel Barclay <dsb@smart.net>
Subject: letting *Man xxx* buffers appear when burying other buffers
Date: Wed, 09 Oct 2002 19:46:47 -0400 [thread overview]
Message-ID: <3DA4BFE7.33BE1085@smart.net> (raw)
In-Reply-To: 20020723185950.7493.9547.Mailman@fencepost.gnu.org
In GNU Emacs 20.7.2, the bury-buffer command treats manual-page
buffers (e.g., *Man xxx*) inconsistently.
Specifically, if you create a manual-page buffer, switch to some
other buffer in that window, and then do:
M-x bury-buffer RET
you don't get back to the first buffer. (In other cases, you
would get back to where you were first.)
How can I eliminate the special-case behavior? (Is there any
configuration variable to set? How can I find the elisp code
for a command?)
(Is there any chance that anyone else would agree that this
"feature" is a bug? (Or its being turned on by default. Or
its being undocumented (in info and in describe-function).
I can imagine that someone got tired of seeing related manual
page buffers after deleting (or burying) source code buffers
and added a special-case fix.
However, behaving specially makes several things inconsistent.
Usually, you can create or raise a number of buffers in
sequence, and then use bury-buffer to return to each previous
buffer. That was a very useful feature. There shouldn't be
any reason you can't use that feature with manual page buffers.
Behaving specially for manual pages is also inconsistent with
delete-buffer: It used to be that both delete-buffer and
bury-buffer left the previous buffer displayed. Now they
diverge.
If this feature is left in, could it at least by controlled
by some configuration variable (a list of buffer types?)?
(If it isn't already.)
Thanks,
Daniel
--
Daniel Barclay
dsb@smart.net
_______________________________________________
Help-gnu-emacs mailing list
Help-gnu-emacs@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnu-emacs
next prev parent reply other threads:[~2002-10-09 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020723185950.7493.9547.Mailman@fencepost.gnu.org>
2002-07-23 19:40 ` letting *Man xxx* buffers appear when burying other buffers Daniel Barclay
2002-10-09 23:46 ` Daniel Barclay [this message]
2002-10-10 2:10 ` David Forrest
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=3DA4BFE7.33BE1085@smart.net \
--to=dsb@smart.net \
/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).