From: Devon Sean McCullough <Emacs-Hacker2017@jovi.net>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 29430@debbugs.gnu.org
Subject: bug#29430: 26.0.90; C-M-backspace is undefined
Date: Fri, 24 Nov 2017 15:35:55 -0500 [thread overview]
Message-ID: <A3A07EA6-8EDE-4083-9EB1-E64F7CA66B5E@jovi.net> (raw)
In-Reply-To: <CAM-tV-8gvaQ4eUAVcyrcjetRSsDR_r4iUFWr6zXBajxTALMhxg@mail.gmail.com>
> On Nov 24, 2017, at 2:28 PM, Noam Postavsky <npostavs@users.sourceforge.net> wrote:
> Seems to be on purpose, bindings.el:1236:
> ;;; These are dangerous in various situations,
> ;;; so let's not encourage anyone to use them.
> ;;;(define-key global-map [C-M-delete] 'backward-kill-sexp)
> ;;;(define-key global-map [C-M-backspace] 'backward-kill-seep)
I doubt those historical reasons still hold
but let's be ultra-cautious — here's a minimal fix:
(unless (eq 'ns (window-system))
;; These were once dangerous in various situations,
;; so let's not encourage just anyone to use them.
(define-key global-map [C-M-delete] 'backward-kill-sexp)
(define-key global-map [C-M-backspace] 'backward-kill-sexp))
Peace
--Devon
P.S. Microsoft apparently considered Ctrl+Alt+Del a security feature,
laughably assuming it would be difficult for malware to intercept it
and steal passwords with a fake login screen.
P.P.S. X11 had a misfeature where Ctrl+Alt+Del nuked all your work
which has been disabled by default for years now in most situations,
e.g.,
https://access.RedHat.com/documentation/en-us/red_hat_enterprise_linux/7/html/desktop_migration_and_administration_guide/enable-ctrl-alt-backspace
https://AskUbuntu.com/questions/367983/how-do-i-enable-ctrl-alt-backspace-to-kill-the-x-server
P.P.P.S. As much as I condemn the imperious cyber-satan at One Infinite Loop,
they set mostly legal and licensing booby traps, seldom technical ones.
next prev parent reply other threads:[~2017-11-24 20:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2017-11-24 20:35 ` Devon Sean McCullough [this message]
2017-11-25 23:14 ` Richard Stallman
2017-11-29 18:02 ` Devon Sean McCullough
2022-03-23 13:30 ` bug#37447: 26.3; Commands on <delete> and <backspace> Lars Ingebrigtsen
2022-03-23 14:35 ` Drew Adams
2022-03-23 14:56 ` bug#37447: bug#29430: " Eli Zaretskii
2022-03-23 20:49 ` bug#29430: " Drew Adams
2022-03-24 6:44 ` Eli Zaretskii
2022-03-24 15:16 ` bug#37447: " Drew Adams
2022-03-24 15:27 ` Eli Zaretskii
2022-03-24 15:51 ` 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=A3A07EA6-8EDE-4083-9EB1-E64F7CA66B5E@jovi.net \
--to=emacs-hacker2017@jovi.net \
--cc=29430@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.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).