From: Eli Zaretskii <eliz@gnu.org>
To: nljlistbox2@gmail.com (N. Jackson)
Cc: 24282@debbugs.gnu.org
Subject: bug#24282: 25.1; Better search overwrapping behaviour for `,' in Info?
Date: Mon, 22 Aug 2016 17:47:30 +0300 [thread overview]
Message-ID: <83h9acc131.fsf@gnu.org> (raw)
In-Reply-To: <87twed6gk4.fsf@moondust.awandering> (nljlistbox2@gmail.com)
> From: nljlistbox2@gmail.com (N. Jackson)
> Date: Sun, 21 Aug 2016 16:57:31 -0300
>
> When doing an index search of an Info manual using `i', the `,' command
> (which cycles through the matches) silently overwraps the search past
> the starting point.
>
> Often when I'm searching, I'll have a vague feeling I've seen the same
> node several times before I realise that my search has overwrapped and
> that I'm just going around in circles.
>
> [The start of the overwrapping is not as easy to spot as it might be
> because the matches seem to be ordered randomly and the same node can
> legitimately occur more than once. (Are they ordered by relevance
> perhaps?)]
>
> I think it would be better (perhaps as an option) if the `,' command
> provided an indication when the search overwraps / would overwrap.
> Perhaps it could just print an error message instead of overwrapping.
> (I'm thinking of isearch's behaviour, when a search would wrap.) A
> message something like:
>
> No more matches, use `,' to continue from start of list.
This is what the stand-alone Info reader does, except that it also
beeps, as when the user makes a mistake. Frankly, I was always
annoyed that Emacs doesn't behave that way, so I'd welcome an option
to make it behave like the stand-alone reader.
Thanks.
next prev parent reply other threads:[~2016-08-22 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 19:57 bug#24282: 25.1; Better search overwrapping behaviour for `,' in Info? N. Jackson
2016-08-22 14:47 ` Eli Zaretskii [this message]
2021-07-06 16:57 ` Lars Ingebrigtsen
2021-07-06 17:18 ` Eli Zaretskii
2016-08-22 14:52 ` Eli Zaretskii
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=83h9acc131.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24282@debbugs.gnu.org \
--cc=nljlistbox2@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).