unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Brand <michael.ch.brand@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Fwd: C-[ is undefined
Date: Wed, 25 Jul 2018 20:00:06 -0600	[thread overview]
Message-ID: <CALn3zogYmq_+SQAXzofw+c+Zns8nL=8oN+6wCkT0E7oDLpux9A@mail.gmail.com> (raw)
In-Reply-To: <CALn3zoj5_bxj2NixizG0_K7pyPo83r=1vrJLa2t9pxHXyR3bGQ@mail.gmail.com>

There seems to be no answer yet but I am still stuck and would
appreciate any help to get further.

---------- Forwarded message ----------
From: Michael Brand <michael.ch.brand@gmail.com>
Date: Sat, Jul 7, 2018 at 1:52 PM
Subject: C-[ is undefined
To: help-gnu-emacs@gnu.org

Hi all

Short story: ~C-x @ c [~ results in "C-[ is undefined" but I expected
it to be the Meta prefix like in for example ~C-[ t~ for ~M-t~.

Long story: With the help of key-chord-mode I started to use two
simultaneously pressed normal keys to get the control modifier:

#+begin_src emacs-lisp
  (defvar v-key-chord-control "en"
    "Key chord for `event-apply-control-modifier'.
  The key chord is optimized for `vi-state' and the Colemak
  keyboard layout (where `en' is QWERTY `jk').")

  (key-chord-define key-translation-map v-key-chord-control
                    #'event-apply-control-modifier)
  (key-chord-define-global v-key-chord-control
                           #'event-apply-control-modifier)
#+end_src

Now also ~en [~ results in "C-[ is undefined". The same applies for \,
], ^ and _ with control modifier. All other control characters (means
a-z with control modifier like for example "en s" for I-search) are
bound as expected.

I tried

#+begin_src emacs-lisp
  (define-key key-translation-map (kbd "C-[") [(escape)])
#+end_src

or

#+begin_src emacs-lisp
  (global-set-key (kbd "C-[") [(escape)])
#+end_src

but ~C-[~ remains undefined. What is the part that I am missing? (And
what will be needed instead of ~[(escape)]~ after the binding is
fixed?)

Please CC me as I am not subscribed to this list.

Michael



  reply	other threads:[~2018-07-26  2:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-07 19:52 C-[ is undefined Michael Brand
2018-07-26  2:00 ` Michael Brand [this message]
     [not found] ` <mailman.4231.1532570417.1292.help-gnu-emacs@gnu.org>
2018-07-26 12:38   ` Fwd: " Ben Bacarisse
2018-07-27  0:17     ` Michael Brand
     [not found]     ` <mailman.4284.1532650678.1292.help-gnu-emacs@gnu.org>
2018-07-27  1:33       ` Ben Bacarisse
2018-07-27 13:24         ` John Shahid
     [not found]         ` <mailman.4322.1532697888.1292.help-gnu-emacs@gnu.org>
2018-07-27 16:19           ` Ben Bacarisse
2018-07-27 13:12 ` Noam Postavsky
2018-07-27 20:38   ` Stefan Monnier
2018-07-28 23:40   ` Michael Brand
2018-08-19 16:02     ` Michael Brand
2018-08-19 16:12       ` Stefan Monnier
2018-08-19 17:01       ` Michael Brand

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='CALn3zogYmq_+SQAXzofw+c+Zns8nL=8oN+6wCkT0E7oDLpux9A@mail.gmail.com' \
    --to=michael.ch.brand@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).