From: Andreas Schwab <schwab@suse.de>
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: key-binding values
Date: Tue, 06 Sep 2005 18:26:38 +0200 [thread overview]
Message-ID: <je7jdu5fi9.fsf@sykes.suse.de> (raw)
In-Reply-To: <MEEKKIABFKKDFJMPIOEBGEMCCMAA.drew.adams@oracle.com> (Drew Adams's message of "Tue, 6 Sep 2005 08:50:53 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> Consider these two definitions:
>
> (defcustom my-key [?\C-\ ] "My key sequence.")
> (defcustom my-key "\C- " "My key sequence.")
>
> `C-h v' then gives these values: [67108896] and "^@".
>
> Is this as good as can be expected - is there no way to get something more
> readable for [?\C-\ ]?
(key-description [67108896]) => "C-SPC"
(key-description "\C- ") => "C-@"
> Emacs users learn quickly to read "^@" as "control @", and they also
> learn that this is equivalent to "control SPC", but [67108896] is hard
> to read and digest.
Keys are just integers in Emacs. There is nothing that makes any integer
special wrt to keys.
> Also, correct me if I'm wrong, but my understanding is that the form [?\C- ]
> is generally preferred over the form "\C- ", for a key binding.
These two key sequences represent quite different bindings. You can't get
one override the other, it depends on the terminal which key you receive
on typing C-space.
> If so, that makes matters worse in cases like this.
>
> This form is good:
>
> (defcustom my-key [(control ?\ )] "My key sequence.")
(key-description [(control ?\ )]) => "C-SPC"
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-09-06 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 15:50 key-binding values Drew Adams
2005-09-06 16:26 ` Andreas Schwab [this message]
2005-09-06 17:15 ` Drew Adams
2005-09-06 22:14 ` Andreas Schwab
2005-09-06 22:51 ` Edward O'Connor
2005-09-07 5:05 ` Richard M. Stallman
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=je7jdu5fi9.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=emacs-devel@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.
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).