unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <help-gnu-emacs@gnu.org>
Subject: RE: How to search all open buffers?
Date: Fri, 31 Aug 2007 18:22:55 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICOEEHDPAA.drew.adams@oracle.com> (raw)
In-Reply-To: <defy23tpt1.fsf@freenet.de>

Wrt searching multiple buffers, in some cases only those visiting files, in
other cases including those not visiting files:

In Icicles, you can use C-c ' (`icicle-occur') to do either. A numeric
prefix arg tells C-c ' to search multiple buffers, not just the current one.
If the arg is 99, then only buffers visiting files are candidates: C-99 C-c
'.

Your minibuffer input filters the candidates when choosing the buffers to
search. You can type a regexp that matches a particular file suffix, to
limit the candidates to file buffers in a given mode.

You can use C-! to select all buffers that match your input, or you can
choose individual buffers that match.

If you often want to search the same set of buffers or files (e.g. for a
project), then you can define the set once, save it, and reuse it later. You
can save it persistently or not.

After you have chosen the buffers to search, you type a pattern (regexp)
that you want to search for. You can change the pattern on the fly - the
search hits are updated incrementally as you type.

C-c ` (`icicle-search') is more general than C-c '. Using it you can search
multiple buffers, multiple files, or multiple regions in different buffers.
You can save such sets of regions for later reuse.

With C-c `, you first parse the target buffers, files, or regions into
search segments using a preliminary regexp, instead of just searching within
all lines as for `occur'. You then search within the segments by typing a
pattern (regexp) to match dynamically (just as for C-c ').

       reply	other threads:[~2007-09-01  1:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <defy23tpt1.fsf@freenet.de>
2007-09-01  1:22 ` Drew Adams [this message]
2007-08-27 20:33 How to search all open buffers? kj
2007-08-27 22:36 ` Eric Hanchrow
2007-08-27 22:57   ` Lennart Borgman (gmail)
2007-08-27 23:32 ` Drew Adams
2007-08-29 15:52   ` Eric Hanchrow
     [not found] ` <fb1e0l$jm0$1@reader1.panix.com>
     [not found]   ` <mailman.5468.1188330586.32220.help-gnu-emacs@gnu.org>
2007-08-29  9:51     ` Richard G Riley
2007-08-30 16:46     ` kj
2007-08-30 21:18       ` Eli Zaretskii
2007-08-30 22:12         ` Dieter Wilhelm
2007-08-31  3:18           ` Eric Hanchrow
2007-08-31  6:08             ` Dieter Wilhelm
2007-08-31 13:07               ` Eric Hanchrow
2007-08-31  8:40           ` Eli Zaretskii
     [not found]       ` <mailman.76.1188508709.18990.help-gnu-emacs@gnu.org>
2007-09-04 13:30         ` kj
2007-09-04 15:51           ` Tom Tromey
2007-09-04 16:45             ` Lennart Borgman (gmail)
2007-09-04 19:03               ` J. David Boyd
2007-09-04 20:38           ` Eli Zaretskii
     [not found]           ` <mailman.323.1188938333.18990.help-gnu-emacs@gnu.org>
2007-09-07 19:16             ` kj

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=DNEMKBNJBGPAOPIJOOICOEEHDPAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@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.
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).