On Fri, Feb 05, 2010 at 09:29:58PM -0500, des...@verizon.net wrote:
> Thomas Adam <thomas.ada...@gmail.com> writes:
>
> > On Fri, Feb 05, 2010 at 08:01:45PM -0500, des...@verizon.net wrote:
> >> "Johann \"Myrkraverk\" Oskarsson" <joh...@myrkraverk.com> writes:
> >>
> >> > On Fri, Feb 5, 2010 at 9:05 PM, <des...@verizon.net> wrote:
> >> >> "Johann \"Myrkraverk\" Oskarsson" <joh...@myrkraverk.com> writes:
> >> >>
> >> >>> On Fri, Feb 5, 2010 at 12:07 PM, Thomas Adam <thomas.ada...@gmail.com>
> >> >>> wrote:
> >> >>>> On 5 February 2010 09:36, Johann "Myrkraverk" Oskarsson
> >> >>>> <joh...@myrkraverk.com> wrote:
> >> >
> >> > Ok, this thread is filled with misunderstanding, and I apolagize for
> >> > not being clearer.
> >> >
> >> > I use the xkb option altwin:meta_win so my windows key actually
> >> > generates the Meta event:
> >> >
> >> > KeyRelease event, serial 142, synthetic NO, window 0x1c00001,
> >> > root 0x1a6, subw 0x0, time 1299299808, (-4,173), root:(696,558),
> >> > state 0x40, keycode 115 (keysym 0xffe7, Meta_L), same_screen YES,
> >> > XLookupString gives 0 bytes:
> >> > XFilterEvent returns: False
> >>
> >> Looks like a keysym, not a modifier.
> >
> > Indeed. But it could all be tied together, with the output from:
> >
> > xmodmap -pm
>
> Indeed. Lots of little knobs to turn.
>
> But how is an ordinary mortal supposed to understand it.
Not sure. Goats and some chanting, presumably. There's really only four
stages to this (I say "only" as though they're easy, but...):
* Look up the keysym via xmodmap.
* Add in an entry for xmodmap to associate the key to a keysym if it never
had one originally.
* Place the key in a modifier slot via xmodmap.
* Bind the thing in FVWM.
But like most things with X11, you always end up having to understand a lot
more of the internals of X than is absolutely necessary. That only adds to
the complexity I suppose.
> For the modifier Mod1, Pk reports the keys:
>
> mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd)
>
> So, I know I have an Alt_L key, and an Alt_R key, but what's
> this Meta_L key? Didn't know I had one so:
>
> me> xmodmap -pke | grep Meta_L
> keycode 64 = Alt_L Meta_L Alt_L Meta_L Alt_L Meta_L
> keycode 205 = NoSymbol Meta_L NoSymbol Meta_L NoSymbol Meta_L
>
> Nice, looks like I have at least 2 Meta_L keys, but
> only when I use a modifier.
Yes -- presumably so you can use it to refer to the modifier key, and the
key itself. Here's an extract from a random Xt.c file I have lying around:
- Any keypress event which contains a modifier bit in its state which is
generated by a keycode whose corresponding keysym is Meta_L or Meta_R
should be interpreted as a "meta" character. Likewise for Super, Hyper,
etc.
- It is illegal for a keysym to be associated with more than one modifier
bit.
This means that the only thing that can reasonably interpret as a
"meta" key is a key whose keysym is Meta_L or Meta_R, and which generates
one of the modifier bits Mod1-Mod5.
Unfortunately, many keyboards don't have Meta keys in their default
configuration. So, if there are no Meta keys, but there are "Alt" keys,
emacs will interpret Alt as Meta. If there are both Meta and Alt keys,
then the Meta keys mean "Meta", and the Alt keys mean "Alt" (it used to
mean "Symbol," but that just confused the hell out of way too many people).
-- Thomas Adam
--
"It was the cruelest game I've ever played and it's played inside my head."
-- "Hush The Warmth", Gorky's Zygotic Mynci.
