From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>, "'Dani Moncayo'" <dmoncayo@gmail.com>
Cc: 9918@debbugs.gnu.org
Subject: bug#9918: 24.0.90; lazy-highlighting in Info mode
Date: Mon, 31 Oct 2011 14:00:03 -0700 [thread overview]
Message-ID: <436BB482340F4A548F73F626446F9DA6@us.oracle.com> (raw)
In-Reply-To: <83sjm8nb79.fsf@gnu.org>
> > >From "emacs -Q":
> > 1. Open Info node "(emacs)Top" (C-h r).
> > 2. Move point to the end of the first paragraph.
> > 3. Type "C-s extensible".
> >
> > The word "extensible" (in the first line of the paragraph) should be
> > lazy-highlighted, as happens if you repeat the experiment
> > after doing "M-x text-mode".
>
> This is a feature. info.el sets isearch-search-fun-function to
> Info-isearch-search, which by default searches in a special way (you
> should see the "Failing I-search" message in the echo are). If you
> don't want this behavior, try customizing Info-isearch-search to nil.
>
> I think this bug report can be closed.
Hm. Obviously this is _not_ TRT from a user point of view. This happens _only_
when there is only one match of the search pattern and that match is before
point. And AFAICT it happens _only_ in Info.
Yes, Isearch forward means Isearch _forward_. But as Dani points out, in other
buffers even a singleton occurrence that precedes point gets highlighted.
This is a bug, IMHO. It should not be closed. Whether it is a high priority
for being fixed is another matter, but it should not be closed just because
Isearch is a bit special in Info. That's just a cop-out. Feature, indeed!
What we should say is "Good catch, Dani - thanks."
next prev parent reply other threads:[~2011-10-31 21:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 14:46 bug#9918: 24.0.90; lazy-highlighting in Info mode Dani Moncayo
2011-10-31 20:43 ` Eli Zaretskii
2011-10-31 21:00 ` Drew Adams [this message]
2011-10-31 21:08 ` Dani Moncayo
2011-10-31 21:13 ` Drew Adams
2011-10-31 21:30 ` Dani Moncayo
2011-10-31 21:39 ` Drew Adams
2011-10-31 23:15 ` Juri Linkov
2011-11-01 9:39 ` Dani Moncayo
2011-11-01 10:21 ` Dani Moncayo
2011-11-01 23:07 ` Juri Linkov
2011-11-02 7:54 ` Dani Moncayo
2011-11-03 9:07 ` Juri Linkov
2011-11-03 9:44 ` Dani Moncayo
2011-11-03 19:24 ` Dani Moncayo
2011-11-03 19:56 ` Juri Linkov
2011-11-03 20:43 ` Dani Moncayo
2011-11-03 21:11 ` Juri Linkov
2011-12-01 7:45 ` Juri Linkov
2011-11-19 21:04 ` Juri Linkov
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=436BB482340F4A548F73F626446F9DA6@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9918@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--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 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).