On 2009-02-17, Paul Hartman <paul.hartman+gen...@gmail.com> wrote: > On Tue, Feb 17, 2009 at 2:00 PM, Grant Edwards <gra...@visi.com> wrote: >> On 2009-02-17, Paul Hartman <paul.hartman+gen...@gmail.com> wrote: >>> On Tue, Feb 17, 2009 at 1:41 PM, Grant Edwards <gra...@visi.com> wrote: >>> >>>> The compose key still works fine in xjed, emacs, rxvt, mrxvt, >>>> xterm, and dozens of GTK and Qt based apps. But, it doesn't >>>> work in aterm or urxvt. >> >> [...] >> >>> I've never owned a keyboard with a "Compose" key, actually I >>> had never even heard of it. >> >> So how do you enter accented or non-latin characters or >> ligatures or the like? > > I don't. The standard US English PC keyboard has nothing but A-Z, > numbers, a few symbols and standard punctuation.
I know. I'm here in the US and have normal USian keyboards. > Typically, if someone has an accented character in their name > or address it is simply entered in without the accent. That just seems a bit parochial. :) > Have to use "character map" type of programs or alternate > keyboard layouts to really enter any "special" characters. Or > the old alt-keypad method from DOS, I don't know if that even > works in Linux. > A quick googling says: > > It looks like the deadkeys problem was a known bug and should have > been fixed in 1.0.1-r2 (there is aterm-1.0.1-deadkeys.patch in the > portage tree). What version did you try? Great! Not sure why I didn't find that when I was Googling earlier. It looks like I'm running 1.0.1-r1. I'll give -r2 a try. > The rxvt-unicode website has a FAQ about the compose key not working: > http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.pod#My_Compose_Multi_key_key_is_no_longe Yea, I found that -- it wasn't really all that helpful. Note to FAQ editors: Saying "X is set wrong" isn't all that helpful if you don't bother to say what the right setting is... -- Grant Edwards grante Yow! WHO sees a BEACH BUNNY at sobbing on a SHAG RUG?! visi.com
