From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 72513 invoked by alias); 10 Jan 2017 13:29:01 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 72486 invoked by uid 89); 10 Jan 2017 13:29:00 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.2 required=5.0 tests=BAYES_40,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=HX-Envelope-From:sk:cygwin., compose, Potential, eats X-HELO: mscha.org Received: from dogbert.mscha.org (HELO mscha.org) (31.25.103.164) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 10 Jan 2017 13:28:50 +0000 Received: from [IPv6:2001:983:8781:1:b852:689:d942:dd42] ([IPv6:2001:983:8781:1:b852:689:d942:dd42]) (authenticated bits=0) by mscha.org (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id v0ADSlgw020894 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 10 Jan 2017 14:28:48 +0100 To: cygwin@cygwin.com From: Michael Schaap Subject: WinCompose vs. Cygwin/X Message-ID: <05386364-2022-02b5-9821-8cfbb59e6733@mscha.org> Date: Tue, 10 Jan 2017 13:29:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2017-01/txt/msg00072.txt.bz2 I recently discovered 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