From: Eli Zaretskii <eliz@gnu.org>
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: Sat, 13 Feb 2021 10:59:24 +0200 [thread overview]
Message-ID: <838s7se42b.fsf@gnu.org> (raw)
In-Reply-To: <87im6wxw11.fsf@gmail.com> (message from Augusto Stoffel on Sat, 13 Feb 2021 08:32:42 +0100)
> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: 46469@debbugs.gnu.org
> Date: Sat, 13 Feb 2021 08:32:42 +0100
>
> On Sat, 13 Feb 2021 at 09:04, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > For isearch-del-char, I think what you see is the intended behavior:
> > that command doesn't undo the effect of the last character you type at
> > the I-search prompt, it just removes the last character of the search
> > string. So it isn't supposed to move point back to where the search
> > started. What you wanted to happen is what isearch-delete-char does.
> >
> > OK?
>
> No, isearch-delete-char is a misnamed command.
I could agree with that, but it's a tangent.
> It undoes the last isearch command, which is typically inserting a
> character OR going to the next/previous match. If you type ‘C-s y
> C-s DEL’ in emacs -q, the search string is still y.
That's true; you need to type DEL twice to actually remove the last
character. But that's how that command was supposed to work, and it
does make sense to me, at least.
> I frankly think DEL should be isearch-del-char by default. I never got
> used to isearch-delete-char in many years before finding out about
> isearch-del-char. But that's besides the point.
>
> As to why the patched version of isearch-delete-char is the "expected"
> or more useful one: this is to a degree a matter of taste, but I can
> give my reasons if you are still not convinced.
If we are talking about personal preferences, then I suggest to make
your desired behavior an opt-in one by introducing a defcustom. We
cannot change the behavior of isearch-del-char unconditionally if the
existing behavior is not a bug, but just something some users may not
like.
Thanks.
next prev parent reply other threads:[~2021-02-13 8:59 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 [this message]
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
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=838s7se42b.fsf@gnu.org \
--to=eliz@gnu.org \
--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).