unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo <sdl.web@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 7718@debbugs.gnu.org
Subject: bug#7718: 23.2.91; Info-isearch-search fails isearch
Date: Sat, 25 Dec 2010 08:39:57 +0000	[thread overview]
Message-ID: <m1sjxmi6ua.fsf@cam.ac.uk> (raw)
In-Reply-To: <87oc8ad1r2.fsf@mail.jurta.org> (Juri Linkov's message of "Sat, 25 Dec 2010 02:28:49 +0000")

On 2010-12-25 02:28 +0000, Juri Linkov wrote:
>>> Info-isearch-search does not implement the noerror arg because it just passes it
>>> unchanged to Info-search.  Do you mean Info-search should implement noerror for
>>> some non-interactive uses?  What it should do when noerror is non-nil?
>>
>> That's what I meant. Info-search doesn't implement noerror. I think it
>> should be like the default isearch search functions:
>> re-/search-forward/backward: Optional argument, if t, means if fail just
>> return nil (no error).
>
> But the whole logic of Isearch using Info-search is built on the
> assumption that Info-search ignores the noerror arg (that is usually t).
> This allow Isearch to fail in the initial Info node
> and to continue searching through other nodes without failing.

For users of isearch-search-string with non-nil noerror it will be a
surprise. For example, I use it before actual isearch to see if the
search is to fail (but don't err) and set things up accordingly. I found
it breaks down in info mode due to its ignoring noerror.

But it is fine if it has to remain that way. I will just wrap
isearch-search-string inside ignore-errors.

Leo





      reply	other threads:[~2010-12-25  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23 10:29 bug#7718: 23.2.91; Info-isearch-search fails isearch Leo
2010-12-23 19:28 ` Juri Linkov
2010-12-23 22:22   ` Leo
2010-12-25  2:28     ` Juri Linkov
2010-12-25  8:39       ` Leo [this message]

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=m1sjxmi6ua.fsf@cam.ac.uk \
    --to=sdl.web@gmail.com \
    --cc=7718@debbugs.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 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).