unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Augusto Stoffel <arstoffel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46469@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#46469: [External] : bug#46469: 27.1; `isearch-del-char' should move point further back
Date: Sun, 14 Feb 2021 08:18:23 +0100	[thread overview]
Message-ID: <878s7rnmm8.fsf@gmail.com> (raw)
In-Reply-To: <83wnvbb9iq.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 14 Feb 2021 05:42:05 +0200")

Re the idea that we can't change the behavior of an old command: if
taken too seriously, this principle would imply that the standard Emacs
UI can never improve; I'm glad this is not the case.  Also,
`isearch-del-char' changed from one obscure key to another obscure key
in Emacs 27.  So clearly things can change.

Re this being a personal preference: I wouldn't bother to send a patch
if I thought so.  As already mentioned, lots of programs copied Emacs's
incremental search, and apparently all changed how DEL works in a
similar way.  This indicates that the patched `isearch-del-char' is what
most people expect (but I'm not suggesting to bind it to DEL, just have
it around for those who want it).

With all that said, could we discuss the merits of the change itself?

If it has a real drawback in comparison with the current
`isearch-del-char', then it would be fine to add a defcustom.  But I
suspect that 3 alternative ways to delete characters from a search
string is a bit over the top.  We can probably come up with a solid
default behavior here.

I already explained my rationale for wanting the change: I mistype
things, but I never hit ‘C-s’ by mistake.  So I want a way to undo just
what I typed.  The current `iserach-del-char' does something slightly
different.  Refer to my third message in this thread for details.

Is there a case where the current behavior is much more convenient
and/or takes the search to a state that can't be easily reproduced by
the patched version?

Thanks,
Augusto





  reply	other threads:[~2021-02-14  7:18 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 [this message]
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=878s7rnmm8.fsf@gmail.com \
    --to=arstoffel@gmail.com \
    --cc=46469@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    /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).