From: "Michael Schaap (lists)" <ml@g.mscha.org>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: WinCompose vs. Cygwin/X
Date: Sat, 24 Jun 2017 22:36:00 -0000 [thread overview]
Message-ID: <CA+Ppj7yiDWNFJhu7S8ERThF_65KjC-P0qn5ALyo95hSZZ_3kZg@mail.gmail.com> (raw)
In-Reply-To: <cb8955dd-31ec-e339-c8a9-66f65ea711d6@dronecode.org.uk>
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
prev parent reply other threads:[~2017-06-24 22:36 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
2017-06-24 22:36 ` Michael Schaap (lists) [this message]
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=CA+Ppj7yiDWNFJhu7S8ERThF_65KjC-P0qn5ALyo95hSZZ_3kZg@mail.gmail.com \
--to=ml@g.mscha.org \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).