Re: Request: Specification For Denoting Keys

[T.V Raman]

thx. Because kbd traces back to reading in recorded kbd macros, it
does more than what a function that you use in defining keys need to
do -- look at edmacro-parse-keys to see what I mean by the above. For
instance, kbd handles things like M-x command-name  that might  have
been invoked while defining or recording a macro.



Stefan Monnier writes:
 > > It gives examples, but it's unclear that it covers all notations that
 > > have been used in the wild over the years --- as in "everything in the
 > > info node is handled by (kbd ...)" but not everything handled by (kbd
 > > ...) is in the info node. I'm not saying that the latter should
 > > happen, I'm looking at what a new parallel ( (call it keyname)
 > > function should be prepared to consume.
 > 
 > I'm not sure I understand what you're getting at, but `kbd` should
 > (hopefully) be the reverse of `key-description`.  IIRC there are a few
 > discrepancies between the two functions, but they should be considered
 > as bugs rather than as features.
 > 
 > 
 >         Stefan

-- 
♉Id: kg:/m/0285kf1  🦮♉

--
♉Id: kg:/m/0285kf1  🦮♉