Hi Frank On Sat, 2003-08-16 at 19:19, Frank Murphy wrote:
> On Saturday 16 August 2003 1:23, Andreas Wüst wrote: > > Well, it kind of worked. I could reach the third group via fn+alt (the > > left one, I don't remember the right one), but, hmm, not all symbols > > worked. For example, I could get [ (fn+alt+5), but I couldn't get ] > > (fn+alt+6). { and } was impossible to reach too. > > > > Strange enough, doing an xmodmap -pke revealed that the keys were mapped > > to the ], {, }, etc. symbols as normal!! But they couldn't be produced! > > Hmm. If you run the program xev, it will print the things it gets for a key > press. Run it and press fn+alt+5 then fn+alt+6. Send us the output of just > the lines that print when you press and release these keys (xev sends a lot > of output). fn+alt+5: KeyPress event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386829502, (53,50), root:(539,353), state 0x0, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES, XLookupString gives 0 characters: "" KeyPress event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386829842, (53,50), root:(539,353), state 0x2000, keycode 14 (keysym 0x5b, bracketleft), same_screen YES, XLookupString gives 1 characters: "[" KeyRelease event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386829902, (53,50), root:(539,353), state 0x2000, keycode 14 (keysym 0x5b, bracketleft), same_screen YES, XLookupString gives 1 characters: "[" KeyRelease event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386830232, (53,50), root:(539,353), state 0x2000, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES, XLookupString gives 0 characters: "" ------------------------------------------------------------------------------- fn+alt+6: KeyPress event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386835101, (53,50), root:(539,353), state 0x0, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES, XLookupString gives 0 characters: "" KeyPress event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386835461, (53,50), root:(539,353), state 0x2000, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES, XLookupString gives 0 characters: "" KeyRelease event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386835530, (53,50), root:(539,353), state 0x2010, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES, XLookupString gives 0 characters: "" KeyRelease event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386835800, (53,50), root:(539,353), state 0x2010, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES, XLookupString gives 0 characters: "" > I assume that these keys work in MacOS? Well, at least they work fine when I xmodmap the Mode_switch to keycode 64. > Also, which keys are { and } on? Third group of 8 ({) and 9 (}). fn+alt+8: KeyPress event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386839549, (53,50), root:(539,353), state 0x10, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES, XLookupString gives 0 characters: "" KeyPress event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386840009, (53,50), root:(539,353), state 0x2010, keycode 80 (keysym 0xff97, KP_Up), same_screen YES, XLookupString gives 0 characters: "" KeyRelease event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386840079, (53,50), root:(539,353), state 0x2010, keycode 80 (keysym 0xff97, KP_Up), same_screen YES, XLookupString gives 0 characters: "" KeyRelease event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386840229, (53,50), root:(539,353), state 0x2010, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES, XLookupString gives 0 characters: "" ------------------------------------------------------------------------------- fn+alt+9: KeyPress event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386842599, (53,50), root:(539,353), state 0x10, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES, XLookupString gives 0 characters: "" KeyPress event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386843008, (53,50), root:(539,353), state 0x2010, keycode 81 (keysym 0xff9a, KP_Prior), same_screen YES, XLookupString gives 0 characters: "" KeyRelease event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386843079, (53,50), root:(539,353), state 0x2010, keycode 81 (keysym 0xff9a, KP_Prior), same_screen YES, XLookupString gives 0 characters: "" KeyRelease event, serial 28, synthetic NO, window 0x1800001, root 0x2d, subw 0x1800002, time 386843348, (53,50), root:(539,353), state 0x2010, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES, XLookupString gives 0 characters: "" As you can see, quite strange keycodes get produced: they were mapped like this (partial output of xmodmap -pke): keycode 9 = Escape keycode 10 = 1 plus plusminus onesuperior keycode 11 = 2 quotedbl twosuperior oneeighth keycode 12 = 3 asterisk numbersign threesuperior keycode 13 = 4 ccedilla Ccedilla keycode 14 = 5 percent bracketleft keycode 15 = 6 ampersand bracketright keycode 16 = 7 slash bar backslash keycode 17 = 8 parenleft braceleft Ograve keycode 18 = 9 parenright braceright Ocircumflex keycode 19 = 0 equal notequal Uacute keycode 64 = Alt_L keycode 77 = Num_Lock Pointer_EnableKeys keycode 80 = KP_8 KP_Up keycode 81 = KP_9 KP_Prior keycode 113 = Mode_switch Multi_key > > > xev will tell you which X keycode and keysym is being sent for a > > > keypress, but you'll need access to an Swiss external Apple keyboard to > > > see the differences between them. > > > > Ok, I guess I am of no help then for this particular issue. > > Yeah, people tend not to have too many keyboards. :) Hehe.. ;) -- Best wishes, Andi