From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org, 1848@emacsbugs.donarmstrong.com, bgoodr@gmail.com
Subject: bug#1848: 23.0.60; isearch-forward fails to find colon characters in Info buffers
Date: Mon, 12 Jan 2009 14:42:35 -0500 [thread overview]
Message-ID: <jwvhc442tzc.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <u8wpgcpk8.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Jan 2009 21:05:59 +0200")
>> >> That's correct, in Emacs 23 C-s doesn't find invisible characters
>> >> in Info. This is an intentional change, not a bug. Please see
>> >> http://thread.gmane.org/gmane.emacs.devel/95142
>>
>> > I found it a bit confusing that setting search-invisible to t makes no
>> > difference to the behaviour here. Should Info-search-success-function
>> > respect search-invisible?
>>
>> I'd say yes. Does anyone object?
> I don't object, but wouldn't it be confusing to have it "find" the
> colon, without the colon being visible? Perhaps we should make it
> temporarily visible?
Oh, yes, definitely. If we can't temporarily show the invisible text,
then we shouldn't obey (eq search-invisible 'open), but we should still
obey (eq search-invisible t).
Stefan
next prev parent reply other threads:[~2009-01-12 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k58x79zl.fsf@jurta.org>
2009-01-10 17:52 ` bug#1848: 23.0.60; isearch-forward fails to find colon characters in Info buffers Brent Goodrick
2009-01-12 1:04 ` Juri Linkov
2009-01-12 8:37 ` Glenn Morris
2009-01-12 15:21 ` Stefan Monnier
2009-01-12 15:25 ` Brent Goodrick
2009-01-12 19:05 ` Eli Zaretskii
2009-01-12 19:42 ` Stefan Monnier [this message]
2009-01-14 1:04 ` Juri Linkov
2009-01-14 1:51 ` Stefan Monnier
2009-01-14 23:25 ` bug#1848: marked as done (23.0.60; isearch-forward fails to find colon characters in Info buffers) Emacs bug Tracking System
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=jwvhc442tzc.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=1848@emacsbugs.donarmstrong.com \
--cc=bgoodr@gmail.com \
--cc=bug-gnu-emacs@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 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.