WinCompose vs. Cygwin/X

Jon Turney
Mon Jan 16 14:49:00 GMT 2017

On 11/01/2017 22:16, Michael Schaap wrote:
> On 11-Jan-17 9:51, Csaba Raduly wrote:
>> Hi Michael,
>> On Tue, Jan 10, 2017 at 2:28 PM, Michael Schaap  wrote:
>>> I recently discovered WinCompose
>>> <>,
>>> a Windows port of XCompose, and fell in love with it.
>>> Unfortunately, it doesn't play nice with Cygwin/X, it seems.
>> (snip various scenarios and potential solutions)

Thanks for reporting this issue.

Unfortunately, this is a complex problem to solve.

At the protocol level, X clients really are being told about 
keypress/release events (i.e. Windows WM_KEYDOWN/WM_KEYUP messages map 
in some way to X11 KeyPress/KeyRelease events)

Now, there is a possible mechanism to tell X clients about characters, 
like the WM_CHAR messages being sent by WinCompose, which is XIM, and 
there was some long-ago work in that area [1], but it's not included in 
current X servers.

>> Have you tried opening an issue in the WinCompose issue tracker? They
>> might be able to code a workaround.
> Somebody beat me to it.  Unfortunately with not much result.

In the short term, some sort of feature in WinCompose where it turns 
itself off for specified windows might be easier.


Jon Turney
Volunteer Cygwin/X X Server maintainer

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list