From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juri Linkov <juri@linkov.net>
Cc: 20092@debbugs.gnu.org, "N. Jackson" <nljlistbox2@gmail.com>
Subject: bug#20092: 24.4.91; False matches with incremental search in Info
Date: Thu, 12 Mar 2015 21:12:08 -0400 [thread overview]
Message-ID: <jwvbnjxsnxx.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <878uf2dmow.fsf@mail.linkov.net> (Juri Linkov's message of "Thu, 12 Mar 2015 21:45:33 +0200")
> Since Info doesn't open invisible text, then maybe `Info-mode' should
> set the buffer-local value of `search-invisible' to nil?
That would work around the problem, yes.
>> I'm not sure what's the best and/or simplest way to fix it.
>> Maybe a first step would be to emit a message explaining that the match
>> is inside hidden text (at least so the user gets a clue about what's
>> going on).
> Like in the message prefix?
[...]
> Or maybe better in the message suffix?
Either way is fine by me. I guess the next step would be to include
some extract of the hidden&matched text, but there's no hurry.
>>> In any case looking at the code, it does actually toggle
>>> (between nil and t), but also changes `open' to nil, and then one can
>>> never "toggle" back to `open'.
>> That's indeed another problem that should be fixed.
> I can't reproduce this problem: after `C-s M-s i M-s i'
> isearch-invisible is still `open'.
So maybe there's no problem on this front after all.
Stefan
next prev parent reply other threads:[~2015-03-13 1:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 0:57 bug#20092: 24.4.91; False matches with incremental search in Info N. Jackson
2015-03-12 3:31 ` N. Jackson
2015-03-12 14:29 ` N. Jackson
2015-03-12 19:16 ` Stefan Monnier
2015-03-12 19:45 ` Juri Linkov
2015-03-13 1:12 ` Stefan Monnier [this message]
2020-08-25 9:40 ` Lars Ingebrigtsen
2020-08-25 18:32 ` Juri Linkov
2021-05-10 11:26 ` Lars Ingebrigtsen
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=jwvbnjxsnxx.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=20092@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=nljlistbox2@gmail.com \
/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).