From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Devon Sean McCullough <Emacs-Hacker2017@jovi.net>
Cc: 29430@debbugs.gnu.org
Subject: bug#29430: 26.0.90; C-M-backspace is undefined
Date: Fri, 24 Nov 2017 14:28:45 -0500 [thread overview]
Message-ID: <CAM-tV-8gvaQ4eUAVcyrcjetRSsDR_r4iUFWr6zXBajxTALMhxg@mail.gmail.com> (raw)
In-Reply-To: <F9C09648-14D4-4AAD-B7D0-A5EF381FD415@jovi.net>
On Fri, Nov 24, 2017 at 2:12 PM, Devon Sean McCullough
<Emacs-Hacker2017@jovi.net> wrote:
> C-M-DEL and ESC C-DEL should both run the same command.
>
> <C-M-backspace> is undefined
>
> ESC <C-backspace> (translated from <escape> <C-backspace>) runs the
> command backward-kill-sexp (found in global-map), which is an
> interactive compiled Lisp function in ‘lisp.el’.
> It is bound to ESC <C-backspace>, ESC <C-delete>.
>
> Peace
> --Devon
>
> P.S. Perhaps a missing translation?
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-sexp)
next prev parent reply other threads:[~2017-11-24 19:28 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 [this message]
2017-11-24 20:35 ` Devon Sean McCullough
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM-tV-8gvaQ4eUAVcyrcjetRSsDR_r4iUFWr6zXBajxTALMhxg@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=29430@debbugs.gnu.org \
--cc=Emacs-Hacker2017@jovi.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 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.