WinCompose vs. Cygwin/X

WinCompose vs. Cygwin/X

[Michael Schaap]

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. WinCompose 
eats the key sequences, and neither the original keys nor the intended 
character(s) ever reach X.
Of course, Cygwin/X has XCompose.  But because of the above, you can't 
use the same compose key in WinCompose and XCompose.  So I keep using 
the wrong compose key.  (gvim is the worst, since I use both the Windows 
and X versions.)

Does any of you have experience with this and know a better way to deal 
with this?
Potential solutions might be to tell Cygwin/X to use Windows keyboard 
handling instead of its own keyboard drivers (but I don't think that's 
possible), or to tell WinCompose to disable itself in windows owned by 
the X server (and that doesn't seem possible either).
(I know mintty has its own compose functionality now, but that doesn't 
help.  I spend a lot of my time in terminal windows, but not all. :)

Thanks in advance,

– Michael

--
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

Re: WinCompose vs. Cygwin/X

[Csaba Raduly]

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)

Have you tried opening an issue in the WinCompose issue tracker? They
might be able to code a workaround.

Csaba
-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

--
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

Re: WinCompose vs. Cygwin/X

[Michael Schaap]

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)
>
> 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

  - Michael

--
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

Re: WinCompose vs. Cygwin/X

[Jon Turney]

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

Re: WinCompose vs. Cygwin/X

[Michael Schaap (lists)]

On 16 January 2017 at 15:49, Jon Turney <jon.turney@dronecode.org.uk> wrote:
> 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)
> In the short term, some sort of feature in WinCompose where it turns itself
> off for specified windows might be easier.

Just a quick note that the latest release of WinCompose (0,7,7) does
exactly that: it turns itself off for windows owned by XWin.exe.
So now WinCompose and XCompose do play nice together.

 - Michael

--
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