Compose key and xterm vs. UTF-8

Roland Smith rsmith at
Sun Mar 14 13:35:55 UTC 2010

On Sun, Mar 14, 2010 at 01:43:27PM +0100, Christian Weisgerber wrote:
> Roland Smith:
> > > Why do compose key sequences fail to work in a UTF-8 xterm?
> > 
> > The port x11/rxvt-unicode is lighter on resources then xterm, and works fine
> > with utf-8. (with LANG=en_US.UTF-8 and LC_ALL=en_US.UTF-8 set)
> You didn't bother to read and understand my question, did you?
> urxvt shows the same poor composing behavior for UTF-8 as xterm
> does.

Make sure that the key you designated as the multi-key really does return that keysym!
My ~/.Xmodmap contains:

    ! Use the right windows key as the Multi-key.
    keycode 0xffec = Multi_key Multi_key
    ! Use the left windows key as the  Meta toets
    keycode 0xffe7 = Meta_L

Use xev(1) to check what symbols the different keys really generate. Then edit
~/.Xmodmap to suite your taste and call 'xmodmap ~/.Xmodmap' to apply the
changes. Make your X startup repeat that to make the changes permanent.

[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url :

More information about the freebsd-questions mailing list