From: Dani Moncayo <dmoncayo@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 9918@debbugs.gnu.org
Subject: bug#9918: 24.0.90; lazy-highlighting in Info mode
Date: Wed, 2 Nov 2011 08:54:12 +0100 [thread overview]
Message-ID: <CAH8Pv0hoVJHXSngtMkF7upcp1X1jb56vymW79YgYMRbrHSa=pw@mail.gmail.com> (raw)
In-Reply-To: <87aa8fo2ko.fsf@mail.jurta.org>
>> 1. Go to Info node "(emacs)Intro".
>> 2. Type "C-s extensible C-s C-s".
>> --> Here you've got the "initial node" message. OK.
>> 3. Type "C-s".
>> --> (Observed) The "initial node" message is removed, and everything
>> remains the same. You have to type "C-s" again to continue the search
>> in subsequent nodes.
>> --> (Expected) The Isearch is continued across subsequent nodes,
>> without the need of an extra "C-s".
>
> The current behavior is correct. When you see the message about failing
> Isearch without the "initial node" suffix, that means that it reached
> the end of the whole manual and failed completely. The subsequent `C-s'
> starts searching from the beginning of the manual.
Ah Ok.
Then, I think that, in this case, a message like "end of the manual"
(analogous to "initial node") would be good, for the user to know
what's going on.
--
Dani Moncayo
next prev parent reply other threads:[~2011-11-02 7:54 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
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 [this message]
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='CAH8Pv0hoVJHXSngtMkF7upcp1X1jb56vymW79YgYMRbrHSa=pw@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=9918@debbugs.gnu.org \
--cc=juri@jurta.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).