[Bug: 21.4.15] global-set-key
james at xemacs.org
Tue Jan 29 11:38:28 EST 2008
On Jan 28, 2008 1:14 AM, Scott Coonce <scott.coonce at samcef.com> wrote:
> I agree with your logic (for 3 = ?\003), but that's not what define-key says.
> My guess is that this isn't so much a bug as a case where the documentation is
> not clear. The doc ( define-key ) says:
> A keysym may be represented by a symbol, or (if and only if it is equivalent
> to an ASCII character in the range 32 - 255) by a character or its equivalent
> ASCII code. [...]
> ===end quote===
> I interpret this to mean that ANY character in the range [32,255] can use it's
> representation (eg. 'a') instead of its ascii code '65'. Since '3' =
> ascii(51), I assumed I could use '3' according to this rule also. Apparently I
> was mistaken.
It is supposed to mean that numbers in the range 32-255 can be used in
place of the character with the corresponding ASCII code. I can
understand the confusion, though. In the 21.5 series, the wording has
been changed to the following:
A key may be represented by a character or its equivalent integer code,
if and only if it is equivalent to a character with a code in the range
32 - 255.
Is that better?
More information about the XEmacs-Beta