From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: Michael Schaap <cygwin.lists@mscha.org>
Subject: Re: WinCompose vs. Cygwin/X
Date: Mon, 16 Jan 2017 14:49:00 -0000 [thread overview]
Message-ID: <cb8955dd-31ec-e339-c8a9-66f65ea711d6@dronecode.org.uk> (raw)
In-Reply-To: <eaa8ac02-1294-d215-6fad-89a33cf2b879@mscha.org>
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
next prev parent reply other threads:[~2017-01-16 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 13:29 Michael Schaap
2017-01-11 8:51 ` Csaba Raduly
2017-01-11 22:16 ` Michael Schaap
2017-01-16 14:49 ` Jon Turney [this message]
2017-06-24 22:36 ` Michael Schaap (lists)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cb8955dd-31ec-e339-c8a9-66f65ea711d6@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin.lists@mscha.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).