unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Marshall, Simon" <simon.marshall@misys.com>
Cc: emacs-devel@gnu.org, 'Andre Spiegel' <spiegel@gnu.org>
Subject: RE: *Occur in buf*?
Date: Mon, 29 Jul 2002 14:52:01 +0100	[thread overview]
Message-ID: <FC3DA3DC8D4AD311AB910020352A8FDC107550A2@eagle.midas-kapiti.com> (raw)

> 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*.

Perhaps that's the best solution, since as you point out we can use it
in other Emacs-generated buffers.  I would find it useful for *VC-log*
buffers when checking in different files at the same time.  Or maybe
vc.el should always use the file buffer name in the temporary log buffer
name.

Perhaps there should be a command similar to rename-uniquely that runs
some function to generate a new name.  Different major modes could set
this function to do the appropriate thing, e.g., M-x occur to use the
original buffer's name; M-x describe-variable to use the variable's
name; etc.

The other suggestions:
Using defadvice (on a function I have to find in replace.el) is not easy
or intuitive.  (Richard, was this what you meant by "customization"?)
Using clone-buffer or rename-uniquely is not what I want---it will
increase the amount of clutter and will not make it easy to find the
buffer in the buffer list.

             reply	other threads:[~2002-07-29 13:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29 13:52 Marshall, Simon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-25 16:07 *Occur in buf*? Marshall, Simon
2002-07-25 18:46 ` Robert J. Chassell
2002-07-25 10:05 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
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

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=FC3DA3DC8D4AD311AB910020352A8FDC107550A2@eagle.midas-kapiti.com \
    --to=simon.marshall@misys.com \
    --cc=emacs-devel@gnu.org \
    --cc=spiegel@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).