From: Juri Linkov <juri@linkov.net>
To: Sebastian Urban <mrsebastianurban@gmail.com>
Cc: 37447@debbugs.gnu.org
Subject: bug#37447: 26.3; Commands on <delete> and <backspace>
Date: Thu, 19 Sep 2019 23:31:21 +0300 [thread overview]
Message-ID: <877e64qgby.fsf@mail.linkov.net> (raw)
In-Reply-To: <14e4c460-b349-00f8-1705-81d89ab4930c@gmail.com> (Sebastian Urban's message of "Wed, 18 Sep 2019 15:18:13 +0200")
>> These key bindings are too old to change them in the default
>> configuration.
>
> So inconsistency with 'M-d' and 'M-<delete>' will stay and
> 'C-<backspace>' & 'M-<backspace>' doing the same thing will also stay
> because of history? I could ignore 'C-S-<backspace>', but previous
> two cases should be "updated".
>
> But if "No." means "No." - close the bug, please. Unless we are
> waiting for more opinions.
Imagine many users using the same keys for years, and now
they will start doing the opposite - a recipe for disaster.
But if a safer solution is possible, then I'd recommend
binding one of C- or M- prefixes to sexp killing commands
because their default prefix C-M- can't be used: C-M-DEL
runs system shutdown, and C-M-<backspace> kills the X server.
There is a replacement C-M-k for kill-sexp, but no key
for backward-kill-sexp.
next prev parent reply other threads:[~2019-09-19 20:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 11:45 bug#37447: 26.3; Commands on <delete> and <backspace> Sebastian Urban
2019-09-18 12:39 ` Eli Zaretskii
2019-09-18 13:18 ` Sebastian Urban
2019-09-19 20:31 ` Juri Linkov [this message]
2019-09-19 21:17 ` Drew Adams
2019-09-19 21:59 ` Noam Postavsky
2019-09-19 22:13 ` Juri Linkov
2019-09-21 15:41 ` Dmitry Gutov
2019-09-20 8:17 ` Sebastian Urban
2019-09-20 8:36 ` Eli Zaretskii
2019-09-20 9:17 ` Sebastian Urban
2019-09-20 9:31 ` Eli Zaretskii
2019-09-20 10:32 ` Sebastian Urban
2019-09-20 12:46 ` Eli Zaretskii
2019-09-20 16:22 ` Sebastian Urban
-- strict thread matches above, loose matches on Subject: below --
2017-11-24 19:12 bug#29430: 26.0.90; C-M-backspace is undefined Devon Sean McCullough
2017-11-24 19:28 ` Noam Postavsky
2022-03-23 13:30 ` bug#37447: 26.3; Commands on <delete> and <backspace> Lars Ingebrigtsen
2022-03-23 14:35 ` Drew Adams
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=877e64qgby.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=37447@debbugs.gnu.org \
--cc=mrsebastianurban@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).