From: Sam Steingold <sds@gnu.org>
Cc: "Marshall, Simon" <simon.marshall@misys.com>,
"'Emacs Developers'" <emacs-devel@gnu.org>
Subject: Re: *Occur in buf*?
Date: 25 Jul 2002 11:01:17 -0400 [thread overview]
Message-ID: <sa0lm7zam2q.fsf@glip.premonitia.com> (raw)
In-Reply-To: <20020725143738.GA26891@gnu.org>
> * In message <20020725143738.GA26891@gnu.org>
> * On the subject of "Re: *Occur in buf*?"
> * Sent on Thu, 25 Jul 2002 10:37:38 -0400
> * Honorable Miles Bader <miles@gnu.org> writes:
>
> On Thu, Jul 25, 2002 at 09:42:16AM -0400, Sam Steingold wrote:
> > > IWBNI M-x occur created an *Occur in buf* buffer so that I wouldn't have
> > > to do this, rather than *Occur*.
> >
> > I like your idea.
> > unless there are objections, I will install the appended patch.
>
> The reason why it's common for commands such as occur to use a global
> buffer is that otherwise you end up with lots of random buffers
> cluttering up things.
this is why I bound 'z' to kill-this-buffer.
as for random buffer clutter, there is midnight.el for that.
> I would suggest to instead make a C-u prefix to occur create a unique
> buffer, and keep the default behavior as-is.
I thought about it. occur uses the prefix argument to indicate the
number of lines, so this is not quite feasible.
> Also note that a more general solution is the `clone-buffer' command,
> which duplicates the current buffer with a unique name; in some modes
> such as info this is bound to M-n (in occur though, M-n is bound to
> `occur-next', though that command actually doesn't seem to work).
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 Steingold (http://www.podval.org/~sds) running RedHat7.3 GNU/Linux
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
Good judgment comes from experience and experience comes from bad judgment.
next prev parent reply other threads:[~2002-07-25 15:01 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 [this message]
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
-- 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=sa0lm7zam2q.fsf@glip.premonitia.com \
--to=sds@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.