Em Ter, 2003-08-05 às 20:41, Frank Murphy escreveu:
> Normally to XFree, I'd think. Unless it's a packaging problem. They're
> responding pretty well to Bugzilla these days (with enough information). But
> it has to be an X bug, of course.
Let me consider it a little bit more, and will do.
> > > Put these into a file .Xmodmap:
> > >
> > > keycode 116 = Meta_L
> > > keycode 64 = Alt_L
> >
> > I gather these are the left-hand keys?
> >
> > Mine got:
> > keycode 115 = Meta_L
> > keycode 108 = Meta_R
> > keycode 64 = Alt_L
>
> So, when you run xev and press the left <option/alt> key, you get something
> like this:
>
> KeyRelease event, serial 27, synthetic NO, window 0x2200001,
> root 0x48, subw 0x0, time 71770797, (2,148), root:(574,566),
> state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
> XLookupString gives 0 characters: ""
Yes:
KeyPress event, serial 23, synthetic NO, window 0x3200001,
root 0x3a, subw 0x0, time 35199642, (337,-3), root:(349,45),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 characters: ""
> But when you press the left <apple logo/command> key, you get:
>
> KeyRelease event, serial 27, synthetic NO, window 0x2200001,
> root 0x48, subw 0x0, time 71826060, (52,144), root:(624,562),
> state 0x40, keycode 115 (keysym 0xffe7, Meta_L), same_screen YES,
> XLookupString gives 0 characters: ""
Yes:
KeyPress event, serial 28, synthetic NO, window 0x3200001,
root 0x3a, subw 0x0, time 35201392, (337,-3), root:(349,45),
state 0x0, keycode 115 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 characters: ""
> If so, it seems to me that Alt is Alt_L and Command is Meta_L as you wanted.
> So perhaps I'm not understanding the problem.
No, it is not. My point is exactly that xmodmap and altwin:meta_win
aren't taking effect in :1, only in :1.
Even wierder still, my machine just froze. I was experimenting with
the console Apple USB keyboard, and when the system went up again, :0
was fine as ever but now I can't do even accented characters in :1. It
looks like, but I'm not sure, :1 is taking the console keyboard
characters. Eerie...
> OK. I think I understand the problem. We're not speaking the same language.
> emacs says Meta, but it often means the <alt> key on the keyboard. X has the
> notion of Alt, Meta, Super, and Hyper, where Alt is the symbol sent when
> pressing the <alt> key and (at least for Debian) Meta when pressing the
> <Apple-logo> key.
This is what I expect, and what I get in :0 but not in :1.
> This might be a problem where the Apple keymaps are not mapping the same as
> the do on x86. I think the <Windows-logo> key sends Super now, but it used to
> send Meta. I'll file a bug with Xfree.
Wait until we are sure of understanding this better.
> ! Rebind keys to permit Alt key to be Meta in Emacs.
That's what I have and don't want...
> Try running it with a -display :1 option. xmodmap is display-dependant. Were
> you running the xmodmap from an xterm on display :1? If so that sounds like
> an xmodmap bug.
Yes, on display :1. I tried with DISPLAY=:1.0, DISPLAY=:1, -display
:1... no joy...
> > Not only GNU Emacs continues to see Alt/Option as Meta in the
> > console, I loose the accented characters I can get with 1. Standard
> > followed by the US International (ISO-8859-15) keymap, us-intl.iso15.
>
> Hmm. On the console, I can use the Alt key as emacs' M- keyprefix.
So do I.
> Is this what you want?
No.
--
_ Leandro Guimarães Faria Corsetti Dutra +41 (21) 648 11 34
/ \ Lausanne, Vaud, Suisse +41 (78) 778 11 34
\ / Brasil +55 (11) 5686 2219
/ \ http://br.geocities.com./lgcdutra/ Soli Deo Gloria!
