From: Dan Nicolaescu <dann@godzilla.ics.uci.edu>
Subject: Re: Info-search-isearch
Date: Mon, 21 Feb 2005 15:47:02 -0800 [thread overview]
Message-ID: <200502212347.j1LNl4AH007049@scanner2.ics.uci.edu> (raw)
In-Reply-To: FDELKNEBLPKKDCEBEJCBKEGJCMAA.drew.adams@oracle.com
"Drew Adams" <drew.adams@oracle.com> writes:
> > Currently only regexp isearch invoked with M-C-s can use
> `Info-search'
> > and search through multiple Info nodes. But it would be better if
> > normal C-s isearch searched through multiple nodes as well.
>
> This would be actually great, it would match the behavior of standalone
> info (which, IMO, is much better).
>
> Is there any reason not to check this code in?
>
> I like being able to confine an isearch to the current node. Currently, I
> can use `s' for global search and `C-s' (or `C-M-s') for local (node)
> search.
>
> So, to me, it would be desirable to have some indication that the end of the
> current node was reached without finding another occurrence of the string -
> e.g. "Failing isearch in node Foo: bar". Except for being able to overwrap
> isearch in the node (no great loss), this would give the advantages of both
> approaches (local and global search). Without such a local-failure
> indication, you would have to (perhaps unwittingly) continue the search to
> another node, and then use `l' to get back where you were.
>
> IOW, why not have two levels of isearch "failure": 1) no more in the current
> node, 2) no more in the current Info "manual"?
The behavior of what you propose is different from either the current
C-s behavior in an emacs info buffer or in standalone info.
The message I was replying to was just asking to make the C-s behavior
the same in an info buffer and standalone info, and allow to the user
to choose one or the other via a customizable variable.
next prev parent reply other threads:[~2005-02-21 23:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 2:21 Info-search-isearch Juri Linkov
2005-02-21 17:54 ` Info-search-isearch Dan Nicolaescu
2005-02-21 18:24 ` Info-search-isearch Drew Adams
2005-02-21 23:47 ` Dan Nicolaescu [this message]
2005-02-22 0:42 ` Info-search-isearch Drew Adams
2005-02-22 18:11 ` Info-search-isearch Richard Stallman
2005-02-22 18:11 ` Info-search-isearch Richard Stallman
2005-02-23 17:34 ` Info-search-isearch Juri Linkov
2005-02-24 13:55 ` Info-search-isearch Richard Stallman
2005-02-25 19:59 ` Info-search-isearch Juri Linkov
2006-10-29 19:10 ` Info-search-isearch Drew Adams
2006-10-29 20:18 ` Info-search-isearch Juri Linkov
2006-10-30 19:17 ` Info-search-isearch Richard Stallman
2006-10-30 19:17 ` Info-search-isearch Richard Stallman
2006-11-01 23:33 ` Info-search-isearch Juri Linkov
2006-11-02 21:47 ` Info-search-isearch Richard Stallman
2006-12-12 16:30 ` word-search toggle for isearch [was: Info-search-isearch] Drew Adams
2006-12-13 3:37 ` Richard Stallman
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=200502212347.j1LNl4AH007049@scanner2.ics.uci.edu \
--to=dann@godzilla.ics.uci.edu \
/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.