From: "Drew Adams" <drew.adams@oracle.com>
To: "'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:39:14 -0700 [thread overview]
Message-ID: <149530B01E1F480EB95B0A56368A2DEB@us.oracle.com> (raw)
In-Reply-To: <CAH8Pv0hn=dKq5R0NuN+9Joq+CPUvdfUS1NRaTrjEn=jpCbE7vw@mail.gmail.com>
> > Note that the problem arises only when there is only one
> > match for the search pattern, and that match occurs before point.
> >
> > E.g.: `g Intro', put point in the 3rd paragraph, then
> > search for `extensible'. There is no problem highlighting
> > occurrences that are before point.
>
> In that case there is no problem, but I think that the reason is that
> the search is succeeding (there is a match in the last paragraph).
> Try to do the same starting from the middle of the last paragraph, and
> you will see the problem again.
Yes. But hit C-s again and it then correctly highlights all of the occurrences
(just as it should have done initially, and which happens in other modes).
It is when there is only a single match that it immediately moves on to the next
node that has a match, instead of highlighting the match in the current node.
At least when there is more than one match a second C-s will highlight them all.
next prev parent reply other threads:[~2011-10-31 21:39 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
2011-10-31 21:13 ` Drew Adams
2011-10-31 21:30 ` Dani Moncayo
2011-10-31 21:39 ` Drew Adams [this message]
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=149530B01E1F480EB95B0A56368A2DEB@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9918@debbugs.gnu.org \
--cc=dmoncayo@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).