From: Michael Schaap <cygwin.lists@mscha.org>
To: cygwin@cygwin.com
Subject: WinCompose vs. Cygwin/X
Date: Tue, 10 Jan 2017 13:29:00 -0000 [thread overview]
Message-ID: <05386364-2022-02b5-9821-8cfbb59e6733@mscha.org> (raw)
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
next reply other threads:[~2017-01-10 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 13:29 Michael Schaap [this message]
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)
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=05386364-2022-02b5-9821-8cfbb59e6733@mscha.org \
--to=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).