On definition of `kbd'

On definition of `kbd'

[Herbert Euler]

I find definition of `kbd' is:

   (defmacro kbd (keys)
     "Convert KEYS to the internal Emacs key representation.
   KEYS should be a string constant in the format used for
   saving keyboard macros (see `edmacro-mode')."
     (read-kbd-macro keys))

This would cause problem when evaluating

  (kbd (car list))

where the `car' of a list is a key sequence text.  Is the
definition correct?  I think the body should be

  `(read-kbd-macro ,keys)

Regards,
Guanpeng Xu

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

Re: On definition of `kbd'

[David Kastrup]

"Herbert Euler" <herberteuler@hotmail.com> writes:

> I find definition of `kbd' is:
>
>   (defmacro kbd (keys)
>     "Convert KEYS to the internal Emacs key representation.
>   KEYS should be a string constant in the format used for
>   saving keyboard macros (see `edmacro-mode')."
>     (read-kbd-macro keys))
>
> This would cause problem when evaluating
>
>  (kbd (car list))
>
> where the `car' of a list is a key sequence text.

In this case, KEYS is the list `(car list)' and not a string constant.

> Is the definition correct?  I think the body should be
>
>  `(read-kbd-macro ,keys)

That would completely defeat the purpose of having a macro, namely
being able to do compile-time evaluation.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: On definition of `kbd'

[Stuart D. Herring]

>> Is the definition correct?  I think the body should be
>>
>>  `(read-kbd-macro ,keys)
>
> That would completely defeat the purpose of having a macro, namely
> being able to do compile-time evaluation.

To elaborate on David's response: if you really want to get a key sequence
representation of a dynamic string, just use the `read-kbd-macro' function
that the `kbd' macro calls.  `kbd' is for when you just want to do
something simple and direct (read: hardcoded) in Lisp: (kbd "C-x C-c"). 
The result is human-readable but during byte-compilation actually becomes
"^X^C" (two characters), so there's no performance penalty.

Hope this helps,
Davis

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.