X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:message-id:date:mime-version :content-type:content-transfer-encoding; q=dns; s=default; b=uzk eXNYA4EBACXHHy9HTGmUKXkNaBMnNHn0OY1ECFu6MsVTnfKrg+DAk+sw5P9Y6+5M SXtF3yo5eHRSI6fmw/aypw5kUN74uR92BmgzUr0zylE2xXQFh/mtoNU9L9xjwL1s JXGZd3fLVQLK/Z7r70uekrYCr8lvJ1YrO/6pWtmI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:message-id:date:mime-version :content-type:content-transfer-encoding; s=default; bh=8h/AMazUW A0m5FsQxQ5G3vhxk3M=; b=inwcv8I9w7RG8ksAmYLSP6xkzWYny+eP1a825TEga kgA92LaT8FEEkyiwhMxwkr+F7UxdoqKVzezUwtaKYn7ZmEe6GVCCRWm3g65ZBfjl iIbgNj46WYk5wnIq6FKZpsaYknFarMiWNUlKEPJlBWf6Tf+2UYpKsCkV9NFPNOLN NM= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 To: cygwin AT cygwin DOT com From: Michael Schaap Subject: WinCompose vs. Cygwin/X Message-ID: <05386364-2022-02b5-9821-8cfbb59e6733@mscha.org> Date: Tue, 10 Jan 2017 14:28:46 +0100 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 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