From: akihisa@mail.ne.jp (Akihisa)
Subject: Re: color-moccur -- multi-buffer occur mode
Date: 25 Nov 2003 19:09:39 -0800 [thread overview]
Message-ID: <96f8e458.0311251909.2bb3ba41@posting.google.com> (raw)
In-Reply-To: jwvad6mbn7l.fsf-monnier+gnu.emacs.sources@vor.iro.umontreal.ca
Stefan Monnier <monnier@iro.umontreal.ca> wrote
> You might want to take a look at the Emacs-CVS code where occur.el
> has been expanded with some kind of multi-occur thingy.
> I haven't looked at your code and neither have I looked at the multi-occur
> thingy in Emacs-CVS, so maybe they have nothing in common other than their
> name, tho.
I didn't know that... So I tried out multi-occur.
I think multi-occur is similar to moccur of color-moccur,
but color-moccur has many advantages.
Interface
- color-moccur:M-x moccur regexp
- multi-occur:M-x multi-occur buffer-name1 buffer-name2... regexp
I have to type buffer-names to search in multi-occur. But I'm too
lazy to type buffer-names.
Goto-Occurrences
multi-occur shows *Occur* buffer. If I'd like to display the
occurrence, I have to type "C-c C-c C-x o" many times. If I use
color-moccur, just type only "j" or "cursor key".
Regexp
To search "(defun multi-occur (" and "(defun moccur (", I have to
type "defun.+occur". In color-moccur (if moccur-split-word is non-nil),
just type "defun occur".
Other functions
dmoccur:open files and run moccur. It's very powerful. You can set a
name and a directory to search (or directories), defalut regexp (or
function to make regexp), to recursively search. It's easy to search
time-string or files in deep directory tree.
But it's complicated to customize.
dired-do-moccur, Buffer-menu-moccur, ibuffer-do-occur
Akihisa Matsushita : akihisa@mail.ne.jp
next prev parent reply other threads:[~2003-11-26 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bpnj1k$bsi$1@caraway.media.kyoto-u.ac.jp>
2003-11-24 0:57 ` color-moccur -- multi-buffer occur mode Stefan Monnier
2003-11-26 3:09 ` Akihisa [this message]
2003-11-26 14:55 ` Stefan Monnier
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=96f8e458.0311251909.2bb3ba41@posting.google.com \
--to=akihisa@mail.ne.jp \
/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).