From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 56535@debbugs.gnu.org, arunlalv04@gmail.com, visuweshm@gmail.com
Subject: bug#56535: 28.1; `no' and `no-ding' values for isearch-wrap-pause option (since Emacs 28.1) not working as documented
Date: Mon, 01 Aug 2022 14:05:01 +0300 [thread overview]
Message-ID: <837d3s442q.fsf@gnu.org> (raw)
In-Reply-To: <867d3t3vha.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 31 Jul 2022 22:58:25 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, visuweshm@gmail.com, 56535@debbugs.gnu.org
> Date: Sun, 31 Jul 2022 22:58:25 +0300
>
> Currently this is documented in the Info node
> (info "(emacs) Repeat Isearch"):
>
> You can control what happens when there are no more matches by
> customizing the ‘isearch-wrap-pause’ user option. If it is ‘t’ (the
> default), signal an error. (Repeating the search will wrap around.) If
> ‘no’, issue a ‘ding’ and wrap immediately after reaching the last match.
> If ‘no-ding’, wrap immediately, but don’t ‘ding’. Finally, if ‘nil’,
> never wrap, but just stop at the last match.
>
> The problem is that everything in this Info node is about
> repeating the search with `C-s C-s'. I can't find a suitable place
> to describe the additional incremental wrapping here.
Why is this node not appropriate for whatever you want to document?
Or maybe I don't have a clear idea of what you want to add there?
next prev parent reply other threads:[~2022-08-01 11:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 7:21 bug#56535: 28.1; `no' and `no-ding' values for isearch-wrap-pause option (since Emacs 28.1) not working as documented Arun V
2022-07-13 12:06 ` Eli Zaretskii
[not found] ` <CABNBW3U9Z-97_fpHK5OcGE=ZvS_W8OQFZkszRMMJO+q5H4B4kQ@mail.gmail.com>
2022-07-13 16:59 ` Eli Zaretskii
2022-07-13 17:22 ` Visuwesh
2022-07-13 17:22 ` Arun V
2022-07-13 17:52 ` Eli Zaretskii
2022-07-13 17:53 ` Arun V
2022-07-13 17:59 ` Arun V
2022-07-13 18:12 ` Eli Zaretskii
2022-07-13 17:59 ` Eli Zaretskii
2022-07-13 18:10 ` Arun V
2022-07-13 19:50 ` Juri Linkov
2022-07-16 9:21 ` Arun V
2022-07-16 16:58 ` Arun V
2022-07-17 19:01 ` Juri Linkov
2022-07-20 16:16 ` Arun V
2022-07-20 17:51 ` Juri Linkov
2022-07-21 19:59 ` Arun V
2022-07-22 7:31 ` Juri Linkov
2022-07-22 9:09 ` Arun V
2022-07-24 16:38 ` Juri Linkov
2022-07-25 7:23 ` Arun V
2022-07-31 17:36 ` Arun V
2022-07-31 19:58 ` Juri Linkov
2022-08-01 11:05 ` Eli Zaretskii [this message]
2022-08-01 17:55 ` Juri Linkov
2022-08-01 18:22 ` Eli Zaretskii
2022-08-01 19:19 ` Juri Linkov
2022-08-02 5:42 ` Arun V
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=837d3s442q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56535@debbugs.gnu.org \
--cc=arunlalv04@gmail.com \
--cc=juri@linkov.net \
--cc=visuweshm@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).