From: Noam Postavsky <npostavs@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Sebastian Urban <mrsebastianurban@gmail.com>,
37447@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#37447: 26.3; Commands on <delete> and <backspace>
Date: Thu, 19 Sep 2019 17:59:29 -0400 [thread overview]
Message-ID: <85o8zgj6bi.fsf@gmail.com> (raw)
In-Reply-To: <077979fb-c46c-495d-9d91-ed94b619cb25@default> (Drew Adams's message of "Thu, 19 Sep 2019 14:17:29 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
>> 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.
> FWIW, `C-M-k' for `kill-sexp', and `C-M-<backspace>
> for `backward-kill-sexp', work on at least some
> platforms, such as MS Windows.
FWIW, recent (since around 2007~2010 from what I see on the web) Xorg
disables C-M-<backspace> as the kill X server by default.
next prev parent reply other threads:[~2019-09-19 21:59 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
2019-09-19 21:17 ` Drew Adams
2019-09-19 21:59 ` Noam Postavsky [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85o8zgj6bi.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=37447@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=juri@linkov.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.