Re: [Bug-mit-scheme] Re: [bug-cscheme] Numlock problem

[Deniz Yuret]

A similar problem seems to exist with the AltGr key of international 
keyboards.  My students use the Turkish Q keyboard and they need to type 
AltGr-3 to get the sharp sign (for #f and #t).  However AltGr gives 
unknown KeySym error.  They are using the current 6.001 version of 
mit-scheme (7.5.1).  Here is the keyboard event that gets generated:


KeyPress event, serial 25, synthetic NO, window 0x2200001,
    root 0x40, subw 0x0, time 1502170, (95,78), root:(840,315),
    state 0x0, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES,
    XLookupString gives 0 bytes:  ""

KeyPress event, serial 25, synthetic NO, window 0x2200001,
    root 0x40, subw 0x0, time 1503371, (95,78), root:(840,315),
    state 0x2000, keycode 12 (keysym 0x23, numbersign), same_screen YES,
    XLookupString gives 1 bytes:  "#"

KeyRelease event, serial 25, synthetic NO, window 0x2200001,
    root 0x40, subw 0x0, time 1503492, (95,78), root:(840,315),
    state 0x2000, keycode 12 (keysym 0x23, numbersign), same_screen YES,
    XLookupString gives 1 bytes:  "#"

KeyRelease event, serial 25, synthetic NO, window 0x2200001,
    root 0x40, subw 0x0, time 1504507, (95,78), root:(840,315),
    state 0x2000, keycode 113 (keysym 0xff7e, Mode_switch), same_screen 
YES,
    XLookupString gives 0 bytes:  ""


From: Chris Hanson
Subject: [Bug-mit-scheme] Re: [bug-cscheme] Numlock problem
Date: Tue, 03 Feb 2004 13:45:18 -0500
User-agent: IMAIL/1.21; Edwin/3.115; MIT-Scheme/7.7.91.pre

   Date: Mon, 2 Feb 2004 16:27:41 -0500 (EST)
   From: "Aaron S. Hawley" <address@hidden>

   I'm still seeing this in Mit Scheme 7.7.90 (edwin 3.114) on Debian
   GNU/Linux.

This is because Num_Lock generates the Mod2 modifier bit, which is
mapped to the "super" bucky bit.

I will disable all of the modifier bit interpretations, except for
mod1, which is "meta".