| 1 |
On Tue, Feb 17, 2009 at 1:41 PM, Grant Edwards <grante@××××.com> wrote: |
| 2 |
> I noticed that the terminal program I've used for years (aterm) |
| 3 |
> recently stopped working with the "compose" key (for generating |
| 4 |
> accented or "foreign" characters, for example). |
| 5 |
> |
| 6 |
> The compose key still works fine in xjed, emacs, rxvt, mrxvt, |
| 7 |
> xterm, and dozens of GTK and Qt based apps. But, it doesn't |
| 8 |
> work in aterm or urxvt. |
| 9 |
> |
| 10 |
> I'm particularly surprised that it works in rxvt (which has |
| 11 |
> been abandoned for years), but not in in rxvt-unicode (built |
| 12 |
> with iso14755 and unicode3 options enabled) which is actively |
| 13 |
> developed and intended to support internationalization. |
| 14 |
> |
| 15 |
> Does anybody else have problems with the compose key and aterm |
| 16 |
> or urxvt? |
| 17 |
|
| 18 |
I've never owned a keyboard with a "Compose" key, actually I had never |
| 19 |
even heard of it. Wikipedia has some info about how you might go about |
| 20 |
setting it up. |
| 21 |
|
| 22 |
http://en.wikipedia.org/wiki/Compose_key |
| 23 |
|
| 24 |
Thanks, |
| 25 |
Paul |
Archives