Subject: bug#2179: 23.0.60; define-key vs define-key-after key syntax

From: Lars Magne Ingebrigtsen <[email-masked]>
Date: Sun, 11 Sep 2011 23:18:20 +0200

Gerard Brunick <[email-masked]> writes:

> (define-key my-map [(control l)] 'do-something)
>
> works as expected, but
>
> (define-key-after my-map [(control l)] 'do-something)
>
> does not.  The reason is that define-key does a lot of work to allow
> for a wide range of key syntaxes, but define-key-after just does:
>
> (setq key
>      (if (<= (length key) 1) (aref key 0) ...
>
> and (control l) must get mapped to ?\C-l = 12 to be useful in a keymap.

Yes, you'd expect both key's to allow the same syntax.  However, as far
as I can see, all the magic to translate from the `define-key' key
syntax is inside that C function, so that would have to be refactored
out first.  I think.

`define-key-after' should at least document the restricted key syntax it
allows... 

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/