From: Juri Linkov <juri@linkov.net>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 46469@debbugs.gnu.org
Subject: bug#46469: 27.1; `isearch-del-char' should move point further back
Date: Thu, 29 Apr 2021 00:37:12 +0300 [thread overview]
Message-ID: <871rau5br7.fsf@mail.linkov.net> (raw)
In-Reply-To: <871raurtyc.fsf@gmail.com> (Augusto Stoffel's message of "Wed, 28 Apr 2021 23:16:11 +0200")
>> But this change will cause a problem to me. Usually, I type 'C-s'
>> several times with a non-empty search string to arrive to Nth occurrence.
>> Then to be able to continue the search with a shorter string, I remove
>> some characters from the search string with 'C-M-d' (isearch-del-char).
>> Then continue searching with 'C-s' from the same place. But with the patch,
>> 'C-M-d' unexpectedly jumps to a previous match, and every next 'C-M-d'
>> jumps back it its previous match that makes no sense.
>
> I can verify this. But I think you just found a related but independent
> issue. Consider this example:
>
> (progn
> (save-excursion (insert "a1 b2 a3"))
> (isearch-mode t t)
> (isearch-printing-char ?a)
> (isearch-repeat-forward)
> (isearch-printing-char ?\\)
> (isearch-printing-char ?|)
> (isearch-printing-char ?b))
>
> When "\\|b" is added to search string, the point is at "3". So it
> shouldn't move, right? But instead it goes back to "2".
>
> Do you get the same behavior?
I tested it in non-regexp mode, and the aforementioned use case is also
for non-regexp mode.
But in the regexp mode, maybe what you found is a bug.
prev parent reply other threads:[~2021-04-28 21:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 18:56 bug#46469: 27.1; `isearch-del-char' should move point further back Augusto Stoffel
2021-02-12 20:00 ` Eli Zaretskii
2021-02-12 20:20 ` Augusto Stoffel
2021-02-13 7:04 ` Eli Zaretskii
2021-02-13 7:32 ` Augusto Stoffel
2021-02-13 8:59 ` Eli Zaretskii
2021-02-13 9:53 ` Augusto Stoffel
2021-02-13 13:28 ` Eli Zaretskii
2021-02-13 23:14 ` bug#46469: [External] : " Drew Adams
2021-02-14 3:42 ` Eli Zaretskii
2021-02-14 7:18 ` Augusto Stoffel
2021-02-14 15:24 ` Eli Zaretskii
2021-02-14 17:49 ` Juri Linkov
2021-02-15 19:31 ` Augusto Stoffel
2021-02-15 19:41 ` Eli Zaretskii
2021-02-13 18:31 ` Juri Linkov
2021-02-14 7:00 ` Augusto Stoffel
2021-02-14 17:45 ` Juri Linkov
2021-04-27 18:44 ` Augusto Stoffel
2021-04-28 20:53 ` Juri Linkov
2021-04-28 21:16 ` Augusto Stoffel
2021-04-28 21:37 ` Juri Linkov [this message]
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=871rau5br7.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=46469@debbugs.gnu.org \
--cc=arstoffel@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).