unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Arun V <arunlalv04@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, visuweshm@gmail.com
Cc: 56535@debbugs.gnu.org
Subject: bug#56535: 28.1; `no' and `no-ding' values for isearch-wrap-pause option (since Emacs 28.1) not working as documented
Date: Wed, 13 Jul 2022 23:29:04 +0530	[thread overview]
Message-ID: <CABNBW3WR9HVvvrL7UXLyvyYrrA-U9Om1R0YxWb4bqzoqx+=O+A@mail.gmail.com> (raw)
In-Reply-To: <CABNBW3U+JYYXTvgn2H2DB+fknbajWhE=rU_nn-1iiD0ZNUBZhA@mail.gmail.com>

When I set the isearch-wrap-pause option to `no' or `no-ding', it
still displays "Failing I-search backward" on entering a non-matching
character. I still have to press C-r again to wrap around. This is the
same behaviour as having set the value of isearch-wrap-pause to t.

On Wed, 13 Jul 2022 at 23:23, Arun V <arunlalv04@gmail.com> wrote:
>
> For more clarity, here's an example.
>
> Assume it's a plain vanilla emacs install with all options set to
> their default values, and it has in it a buffer with the following
> content (of just 3 lines).
>
> Line one of buffer
> Line two of buffer
> Line three of buffer
>
> If the point is at the beginning of the second line, and we issue a
> C-r and start typing the following characters "L", "i", "n", "e", " ",
> the point would be moved to the first line. If we continue to type
> "t", the minibuffer will display "Failing I-search backward" and the
> point will still remain on the first line. If we press C-r again, the
> minibuffer will display "Wrapped I-search backward" and move the point
> to the third line.
>
> This is the default behaviour (with isearch-wrap-pause set to t). I
> can see the documented behaviour when I set the value to nil i.e. no
> wrap around.
>
> But when I set the value to `no' or `no-ding', I was expecting the
> point to automatically move to the third line immediately after typing
> "t" as mentioned in the above use case. Atleast, this is what I could
> understand from the documentation. Please correct me if I'm wrong.
>
> On Wed, 13 Jul 2022 at 22:52, Arun V <arunlalv04@gmail.com> wrote:
> >
> > Typing C-s over and over does wrap around at the end of the buffer.
> > But that shouldn't be the behaviour when isearch-wrap-pause is set to
> > `no' or `no-ding', right?
> >
> > The following is an excerpt from the documentation I'm referring to
> > [https://www.gnu.org/software/emacs/manual/html_node/emacs/Repeat-Isearch.html]
> >
> > "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."
> >
> > Please let me know if I'm missing anything here.
> >
> >
> > On Wed, 13 Jul 2022 at 22:29, Eli Zaretskii <eliz@gnu.org> wrote:
> > >
> > > [Please use Reply All to keep the bug tracker on the CC list.]
> > >
> > > > From: Arun V <arunlalv04@gmail.com>
> > > > Date: Wed, 13 Jul 2022 21:32:08 +0530
> > > >
> > > > Hi Eli,
> > > >
> > > > Shall I share screenshots?
> > > > I'm able to reproduce this in plain vanilla emacs in Windows and Linux.
> > >
> > > There's no need to show a screenshot, I believe you.  It's just that I
> > > cannot reproduce the problem: typing C-s over and over wraps around at
> > > the end of the buffer and goes to the beginning.  So I wonder what is
> > > different on your system that makes this not work.
> >
> >
> >
> > --
> > --
> > Thanks and regards,
> > Arunlal Venugopal
>
>
>
> --
> --
> Thanks and regards,
> Arunlal Venugopal



-- 
--
Thanks and regards,
Arunlal Venugopal





  reply	other threads:[~2022-07-13 17:59 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 [this message]
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
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='CABNBW3WR9HVvvrL7UXLyvyYrrA-U9Om1R0YxWb4bqzoqx+=O+A@mail.gmail.com' \
    --to=arunlalv04@gmail.com \
    --cc=56535@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).