unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Random832 <random832@fastmail.com>
To: emacs-devel@gnu.org
Subject: Re: Is `kbd' idempotent?
Date: Mon, 30 Nov 2015 16:24:05 +0000 (UTC)	[thread overview]
Message-ID: <n3ht74$lu$1@ger.gmane.org> (raw)
In-Reply-To: 87610jqxx6.fsf@web.de

On 2015-11-30, Michael Heerdegen <michael_heerdegen@web.de> wrote:
> Mmh, maybe it should better ask: if KEYS is a string that describes a
> key sequence in any format that Emacs understands, or in the format that
> is used for keyboard macros, and I call `kbd' on it, is the result
> always a representation of same key sequence?  The docstring of `kbd'
> leaves open what it does with formats different from the keyboard macro
> format.  Or is there any test that I could use to decide whether KEYS is
> in the keyboard macro format?

What exactly do you define as "any format that Emacs
understands" - do you want to allow backslash-escapes (even
though no characters requiring such are used in keyboard macro
format)? Control characters typed directly with C-q? A vector
literal such as "[?\\M-x]" representing [134217848]? The string
"(kbd \"foo\")"? Emacs understands all of these.

Basically, what other formats, specifically, do you want to
accept? What formats do you think your documentation will cause
your users to be inclined to type?




  reply	other threads:[~2015-11-30 16:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 15:26 Is `kbd' idempotent? Michael Heerdegen
2015-11-30 15:39 ` David Kastrup
2015-11-30 16:01   ` Michael Heerdegen
2015-11-30 16:24     ` Random832 [this message]
2015-12-01 14:25       ` Michael Heerdegen
2015-12-01 15:37         ` Random832
2015-12-01 18:32           ` Michael Heerdegen
2015-12-02 18:33           ` Michael Heerdegen
2015-11-30 16:24     ` Andreas Schwab
2015-11-30 16:30 ` Random832

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='n3ht74$lu$1@ger.gmane.org' \
    --to=random832@fastmail.com \
    --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).