unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13592@debbugs.gnu.org
Subject: bug#13592: 24.2.92; C-s prompts with "Multi I-search:" today
Date: Thu, 31 Jan 2013 02:34:03 +0200	[thread overview]
Message-ID: <87libamat2.fsf@mail.jurta.org> (raw)
In-Reply-To: <83pq0mh5ex.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 30 Jan 2013 20:49:58 +0200")

>  . Why is it a good idea to show this Multi thing at the very
>    beginning of the search, when there's no evidence whatsoever that
>    the search is in danger of crossing into the next file in the
>    series?  It's confusing to see this, because _I_ didn't ask for
>    multi-file or multibuffer isearch.  It took me by surprise and
>    forced me to go looking for the reason (tried in other versions of
>    Emacs and in other buffers, before it dawned on me that it is
>    something specific to add-log mode).  You want to be nice to me?
>    fine: then show this to me when I type C-s that will cross into the
>    next file, but not before that.

When you type C-s that will cross into the next file,
it appends this text to the isearch message:

  [repeat for next buffer]

>    _Then_ I might appreciate the service.  But when I type my first C-s,
>    please give me just what I asked for.

Multi-file isearch is a special kind of search, so the prefix "Multi"
informs the user that the search will go through a set of files.
This is like the prefix "Regexp" informing the user that the search
is regexp-based, and other informative prefixes as well.

>  . This should at least be documented in the manual.  When I saw this
>    prompt, I tried to figure out what it meant (did someone really
>    think that "Multi" explains it all?), but it seems not to be
>    mentioned anywhere in the docs.  Even the NEWS entry for Emacs
>    23.1, which does say that isearch is automatically multi-file in
>    ChangeLog files, doesn't mention this prompt.  I needed to wade
>    through isearch.el to find what it meant, only to find out that the
>    facility used to trigger it -- multi-search-next-buffer-function --
>    is not documented in the Elisp manual, either, which sounds weird
>    if we consider such features useful in other modes.

It could be documented in (info "(emacs) Other Repeating Search")
where `multi-isearch-buffers' is already described.





  parent reply	other threads:[~2013-01-31  0:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 18:49 bug#13592: 24.2.92; C-s prompts with "Multi I-search:" today Eli Zaretskii
2013-01-30 19:08 ` Drew Adams
2013-01-31  0:34 ` Juri Linkov [this message]
2013-01-31  3:56   ` Eli Zaretskii
2013-01-31 23:58     ` Juri Linkov
2013-02-01  7:57       ` Eli Zaretskii
2013-02-01 23:44         ` Juri Linkov
2013-02-02  9:46           ` Eli Zaretskii
2014-11-09 19:20             ` 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

  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=87libamat2.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=13592@debbugs.gnu.org \
    --cc=eliz@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).