On Tue, Jan 14, 2014 at 02:27:37PM +0100, François Patte <[email protected]> wrote: > > There is nothing special you need to do to enable dead keys, they work out > > of > > the box unless they are disabled somehow. > > As they are not working, they must be disabled somewhere... but where?
I must admit I don't know then - urxvt is not responsible for dead keys, it's your xlib and your configuration. On Tue, Jan 14, 2014 at 02:33:40PM +0100, fa-ml <[email protected]> wrote: > I had a similar problem after installing Debian Wheezy and trying to configure > a CJK input method (via ibus). Do you happen to be in the same situation? > What helped me was to to launch rxvt-unicode like: > > XMODIFIERS="" urxvt > > Even though it's a workaround rather than a solution If XMODIFIERS are set to use some input method, then urxvt will use the input method as configured. If the input method doesn't do dead keys, then urxvt will not have dead key support either. So if that is the case, then properly setting (or clearing) XMODIFIERS is the solution - urxvt can only go by what it is being told to use. urxvt has more support for x input methods than xterm or most gui apps (which don't normally use x input methods at all). That might explain why xterm works - it will not see the input method, and just use the standard kexyboard mapping. Likewise other terminals. -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / [email protected] -=====/_/_//_/\_,_/ /_/\_\ _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
