From: storm@cua.dk (Kim F. Storm)
Cc: simon.marshall@misys.com, emacs-devel@gnu.org
Subject: Re: *Occur in buf*?
Date: 28 Jul 2002 02:15:01 +0200 [thread overview]
Message-ID: <5xd6t83dyy.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200207261536.g6QFa4U08962@aztec.santafe.edu>
Richard Stallman <rms@gnu.org> writes:
> IWBNI M-x occur created an *Occur in buf* buffer so that I wouldn't have
> to do this, rather than *Occur*.
>
> I think that for most users this would create unnecessary clutter.
> Perhaps it is best if you simply do this as a customization.
Alternatively, always name the buffer *Occur*, but provide a occur-save-buffer
command (bound to `s') which renames the buffer to *Occur: buffer*; then the
user can easily save precious occur buffers on a needed basis.
The same could be done for *Help* buffers where it would sometimes be very
useful to keep multiple help buffer around, e.g. *Help: save-buffer* and
*Help: bury-buffer*.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-07-28 0:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 10:05 *Occur in buf*? Marshall, Simon
2002-07-25 13:42 ` Sam Steingold
2002-07-25 14:37 ` Miles Bader
2002-07-25 15:01 ` Sam Steingold
2002-07-26 15:36 ` Richard Stallman
2002-07-26 19:53 ` Sam Steingold
2002-07-26 15:36 ` Richard Stallman
2002-07-26 17:53 ` Benjamin Rutt
2002-07-28 0:15 ` Kim F. Storm [this message]
2002-07-28 1:10 ` Miles Bader
2002-07-29 8:31 ` Kim F. Storm
2002-07-30 14:20 ` Sam Steingold
2002-07-31 1:36 ` Miles Bader
2002-07-31 5:54 ` Richard Stallman
2002-07-31 15:33 ` Sam Steingold
2002-08-09 7:32 ` Stefan Monnier
2002-08-09 7:34 ` Stefan Monnier
2002-07-29 1:42 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2002-07-25 16:07 Marshall, Simon
2002-07-25 18:46 ` Robert J. Chassell
2002-07-29 13:52 Marshall, Simon
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=5xd6t83dyy.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=simon.marshall@misys.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).