unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: RE: isearch-forward and Info-search
Date: Fri, 11 Mar 2005 06:40:40 -0800	[thread overview]
Message-ID: <FDELKNEBLPKKDCEBEJCBAEEHCNAA.drew.adams@oracle.com> (raw)
In-Reply-To: <877jkfq7v0.fsf@jurta.org>

    >     Would you like it if isearch failed before proceeding to the
    >     next Info node?
    >
    > I would. I suggested this long ago. It should first wrap, as Richard
    > suggested. After the entire Info node has been searched, it should
    > fail. A subsequent invocation should continue through the manual.
    > IOW, isearch the node completely first (wrapping), then inform the
    > user that there are no more occurrences in the node, then continue
    > on to other nodes.

    IMO, this behavior is too confusing.

I agree, and I don't know why I suggested here to first wrap. In fact, what
you describe was what I suggested originally:

          > But it would be better if
          > normal C-s isearch searched through multiple nodes as well.

    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)....
    IOW, why not have two levels of isearch "failure": 1) no more
    in the current node, 2) no more in the current Info "manual"?

  parent reply	other threads:[~2005-03-11 14:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  7:32 isearch-forward and Info-search Nick Roberts
2005-03-09  7:59 ` Miles Bader
2005-03-10  2:02   ` Richard Stallman
2005-03-10  6:29   ` Juri Linkov
2005-03-10  7:56     ` Nick Roberts
2005-03-10 17:20     ` Drew Adams
2005-03-11  1:48     ` Richard Stallman
2005-03-10  6:33 ` Juri Linkov
2005-03-10 17:19   ` Drew Adams
2005-03-11  7:28     ` Juri Linkov
2005-03-11  8:15       ` Nick Roberts
2005-03-11 14:40       ` Drew Adams [this message]
2005-03-12  2:23 ` Juri Linkov
2005-03-12 13:47   ` Stefan Monnier
2005-03-13  1:00     ` Juri Linkov
2005-03-13 21:15       ` Nick Roberts
2005-03-29 12:17       ` Kai Großjohann
2005-03-29 13:48         ` 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=FDELKNEBLPKKDCEBEJCBAEEHCNAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@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).