Re: WinCompose vs. Cygwin/X

[Jon Turney <jon dot turney at dronecode dot org dot uk>]

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
> > > <https://github.com/samhocevar/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.
> https://github.com/samhocevar/wincompose/issues/132

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

[1] https://www.cygwin.com/ml/cygwin-xfree/2005-01/msg00066.html

--
Jon Turney
Volunteer Cygwin/X X Server maintainer

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple