unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: defcustom :type to use for a key sequence?
Date: Fri, 4 Nov 2005 16:29:04 -0800	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICIEGFCOAA.drew.adams@oracle.com> (raw)
In-Reply-To: <MEEKKIABFKKDFJMPIOEBGEEHCNAA.drew.adams@oracle.com>

Resending, hoping someone can help.  Thx.

--- 

    Suppose I have this:
    
    (defcustom the-key [(meta ?\ )] "...")
    (define-key my-map the-key 'the-cmd))
    
    A user might customize which key sequence is bound to `the-cmd'.
    
    What :type is appropriate for the defcustom? I don't see a type 
    ready-made for key sequences.  Just `string'?  Or is a `choice' of 
    `string' and (what kind of?) `vector' appropriate?  How can the
    :type allow for any key sequence (besides using just `sexp')?  Thx.

      reply	other threads:[~2005-11-05  0:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 19:49 defcustom :type to use for a key sequence? Drew Adams
2005-11-05  0:29 ` Drew Adams [this message]

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=DNEMKBNJBGPAOPIJOOICIEGFCOAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    /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).