Hi, Xianwen Chen wrote on Wed, Feb 19, 2020 at 10:37:58AM +0000:
> I run OpenBSD 6.6 amd64. I'm trying to reproduce on OpenBSD-current. > The window manager is fvwm I'm using that, too. > with stock configuration. Well, my configuration is much less bloated than the default (125 rather than 491 lines). But that shouldn't make a difference. > I am not able to completely set compose key by > > $ setxkbmap -layout us -variant dvp -option compose:ralt Just to make sure it worked, could you please show the output of: $ setxkbmap -query > What I meant by *not completely* is that I am able to use _right alt_ > as the compose key on for example Firefox. However, on xterm, I am not > able to use the compose key. It certainly works for me. What exactly do you mean by "not able to use"? If, while xterm is in focus, you press and relese the compose key, then press and release the first key, then press and release the second key, then press and release some latin letter key, what exactly happens after each step? Guessing blindly, the problem might be that while firefox finds a font to display the character, xterm does not. Or that you have changed your xterm configuration in some way that disables UTF-8 (it is on by default). Can you please retry in xterm with a different character that can be displayed in xterm out of the box, say U+00E5 LATIN SMALL LETTER A WITH RING ABOVE? What happens if you type and release ralt, then a, then a, then x? If none of the above lets you solve your problem yet, what does the following command say: $ xterm -report-xres In an xterm started that way, does the compose key work? Both with the character you want and with U+00E5 A RING? Yours, Ingo
