From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9918@debbugs.gnu.org
Subject: bug#9918: 24.0.90; lazy-highlighting in Info mode
Date: Mon, 31 Oct 2011 22:08:17 +0100 [thread overview]
Message-ID: <CAH8Pv0ivcTRUwbp-T4shUWprKcBumNuYsTm8nG3mVSOfp3r4-Q@mail.gmail.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
IMO, it would be better if that special way of searching was
consistent with the standard Isearch wrt the lazy highlighting.
In step #3 above, the lazy highlighting is performed well until the
search begins to fail, point at which the lazy highlighting is
deactivated. As I said, this behavior is (a) inconsistent with the
standard Isearch (try to do the same in text mode) and (b) less
informative for the user (there is indeed a match of "extensible" that
should be advised to the user).
--
Dani Moncayo
next prev parent reply other threads:[~2011-10-31 21:08 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
2011-10-31 21:08 ` Dani Moncayo [this message]
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=CAH8Pv0ivcTRUwbp-T4shUWprKcBumNuYsTm8nG3mVSOfp3r4-Q@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=9918@debbugs.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 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).