xterm ignores Meta key

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'd like to post with an address different from my subscription
address.  Is there a post-only list I can subscribe my posting address
to?

I'm running XFree86 4.2.1, and xterm seem to ignore the Meta
modifier.  Emacs has no problem with Meta-modified key, and xev seems
to get them ok.  When I type Meta-b, I get:

KeyPress event, serial 18, synthetic NO, window 0x1200001,
    root 0x39, subw 0x0, time 1770620779, (22,177), root:(313,468),
    state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 characters:  ""

KeyPress event, serial 18, synthetic NO, window 0x1200001,
    root 0x39, subw 0x0, time 1770621076, (22,177), root:(313,468),
    state 0x8, keycode 56 (keysym 0x62, b), same_screen YES,
    XLookupString gives 1 characters:  "b"

KeyRelease event, serial 18, synthetic NO, window 0x1200001,
    root 0x39, subw 0x0, time 1770621169, (22,177), root:(313,468),
    state 0x8, keycode 56 (keysym 0x62, b), same_screen YES,
    XLookupString gives 1 characters:  "b"

KeyRelease event, serial 18, synthetic NO, window 0x1200001,
    root 0x39, subw 0x0, time 1770621559, (22,177), root:(313,468),
    state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 characters:  ""

It does seem odd that XLookupString gives an unmodified b when the
state is 0x8, but I don't know if that's a problem.  When I type a
Control-modified character, xev outputs the control character itself
for XLookupString.  But when I run anything in an xterm (cat, bash,
emacs), Meta-modified keys are treated just like unmodified keys.
I've tried all four combinations of eightBitInput and metaSendsEscape
with no luck.

I built X (and the rest of the system) from source myself.  The first
few times I ran it, I didn't have this problem.  But after I finished
setting up my xdm/server configuration, this started happening.  (And
somehow I reproduced the problem on another machine with different
hardware when I finished setting up a similar configuration there.)  I
don't know which configuration change triggered it.  At the same time,
I started getting a problem where "xset r rate ..." would segfault and
the server would output an error message from xkbcomp.  Sorry, I don't
have the message anymore; I think it was something about a "(null)"
filename.  Since this error involved xkbcomp, I tried rebuilding X
with BuildXKB as NO.  After that, xset worked, but xterm still doesn't
see Meta.  xf86config attached.  Any ideas?


paul
_______________________________________________

Newbie@XFree86.Org
*** To unsubscribe , or change message options, see:
http://XFree86.Org/mailman/listinfo/newbie

[Index of Archives]     [XFree86]     [Xfree86 Xpert]     [X.org]     [IETF Annouce]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Picture Sharing]     [Linux Security]     [Linux RAID]

  Powered by Linux