From: "Tobias C. Rittweiler" <tcr@freebits.de>
To: emacs-devel@gnu.org
Cc: Juri Linkov <juri@jurta.org>
Subject: Comments on misearch.el
Date: Tue, 17 Nov 2009 16:22:25 +0100 [thread overview]
Message-ID: <87iqd9mb0u.fsf@freebits.de> (raw)
I just tried misearch.el which provides the ability to search through
multiple files / buffers via isearch. Thank you, Juri, for writing it,
it's exactly what I need.
(BTW., is there something like misearch but for query-replace, too?)
I do have some comments on it:
* The docstring of `multi-isearch-next-buffer-function' says that the
function is called with the current buffer as first argument.
However, in case of the initial buffer, it's actually called with
`nil' as first argument.
Is that intended? If so, the docstring should reflect that.
I now have in my next-buffer function
(setq current-buffer (or current-buffer (current-buffer)))
as a workaround.
* It'd be nice, not only to display "Repeat for next buffer", but
actually include the next buffer's name.
* If I'm in a file that contains matches, and I'm at the last match,
it exhibits the following behaviour in the minibuffer:
Multi Isearch: ... (pressing C-s)
Failing multi Isearch: ... [Repeat ...] (pressing C-s)
jumps to first match in next buffer
However, if I'm in a buffer that won't have a match, I see the
following behaviour:
Multi Isearch: ..(incremently typing).. --> turns to
Failing multi Isearch: ... [Repeat ...] (pressing C-s)
Failing mutli Isearch: ... (pressing C-s)
goes to next file
I.e., as you can hopefully see, it expects one C-s too much. (The
line without the "[Repeat ...]" is superfluous.)
-T.
next reply other threads:[~2009-11-17 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 15:22 Tobias C. Rittweiler [this message]
2009-11-17 17:54 ` Comments on misearch.el Juri Linkov
2009-11-17 18:52 ` Tobias C. Rittweiler
2009-11-18 9:56 ` tags-query-replace (was: Comments on misearch.el) Juri Linkov
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=87iqd9mb0u.fsf@freebits.de \
--to=tcr@freebits.de \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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 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.