unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Marshall, Simon" <simon.marshall@misys.com>
Cc: 'Emacs Developers' <emacs-devel@gnu.org>
Subject: RE: *Occur in buf*?
Date: Thu, 25 Jul 2002 17:07:34 +0100	[thread overview]
Message-ID: <FC3DA3DC8D4AD311AB910020352A8FDC1075509D@eagle.midas-kapiti.com> (raw)

> I can add an `occur-rename' command (bound to `r') that would 
> rename the
> occur buffer as proposed and bind `clone-buffer' to 'c'.
> do you like this better?
> then the effect of my original patch can be accomplished by adding
> `occur-rename' to `occur-mode-hook'.

Sam, thanks for the suggestions.

I thought that this renaming might be optional, i.e., current behaviour
by default.  I was thinking in terms of a user variable rather than
adding to a hook.

But, I'm not sure how clean the Occur buffer key (to rename the *Occur*
buffer to *Occur: buf*) would actually be.  Suppose M-x occur simply
created an *Occur* buffer.  Suppose I was to rename one to *Occur: buf*
by using the key.  Then, I did another M-x occur (maybe for a different
regexp).  Should M-x occur create another *Occur* buffer?  Or reuse the
*Occur: buf* buffer?  The answer, of course, depends on what I happen to
feel like at the time.  Whichever it chooses will annoy me some of the
time.  "Damn, it went and created yet another buffer!"  Or "damn, it
overwrote my previous M-x occur buffer!".  M-x occur cannot know if I
had renamed the original *Occur* buffer so that *Occur: buf* is the
buffer I want for future M-x occur output or so that I could keep/save
that particular *Occur* buffer only.

Perhaps, in this case, it should create another *Occur* buffer.  If the
user uses the key again to rename it to *Occur: buf*, should Emacs
silently remove the old *Occur: buf* buffer?

Maybe it needs some more thought.

BTW, I prefer *Occur: buf* to *Occur:buf* though YMMV.
I find it easier to spot the original buffer name.
It follows the convention of other buffer names I've seen.

             reply	other threads:[~2002-07-25 16:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25 16:07 Marshall, Simon [this message]
2002-07-25 18:46 ` *Occur in buf*? Robert J. Chassell
  -- strict thread matches above, loose matches on Subject: below --
2002-07-29 13:52 Marshall, Simon
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=FC3DA3DC8D4AD311AB910020352A8FDC1075509D@eagle.midas-kapiti.com \
    --to=simon.marshall@misys.com \
    --cc=emacs-devel@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).