From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <CAOEdRO3tJua4+Sk=q1B5Az4Z2O4+Vu1ODp1Ep-iDx2gTrT+V0Q@mail.gmail.com>
References: <CAOEdRO3tJua4+Sk=q1B5Az4Z2O4+Vu1ODp1Ep-iDx2gTrT+V0Q@mail.gmail.com>
Date: Thu, 22 Jan 2015 09:18:57 +0100
Message-ID: <CAOEdRO1XAz+g_88os9ePs7ZB8yM3Su_OsHO7ih1TL8dH39FpMA@mail.gmail.com>
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [9fans] plan9port .XCompose suddenly doesn't work
Topicbox-Message-UUID: 3b11af5e-ead9-11e9-9d60-3106f5b1d025

I am puzzled. Anyway, it actually works in acme too,
but differently than I remember from before.

I now have to press and *release* the compose key
and then continue; i.e. to write alpha I have to
- press left alt (my compose key)
- release left alt
- press shift and 8 (together it's *)
- release those
- press a

This is different from the behaviour in xterm, where the
compose key can be hold down during the step of shift+8.

So at least it works somehow.

Ruda



On 21 January 2015 at 17:12, Rudolf Sykora <rudolf.sykora@gmail.com> wrote:
> Hello,
>
> until recently I happily used a generated ~/.XCompose file on p9p
> (see http://swtch.com/plan9port/man/man7/keyboard.html)
> to be able to write various characters in a way similar to p9.
> But now something must have changed.
> I can use the composition in, say, xterm (it works),
> but when I start acme (or sam), it doesn't work.
>
> Contrary to running xterm, I do not see anything in the
> output of
>
> strace -e open acme |& grep Compose
>
>
> Does somebody have a clue?
>
> Thanks
> Ruda