From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 71010 invoked by alias); 16 Jan 2017 14:49:28 -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 70991 invoked by uid 89); 16 Jan 2017 14:49:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=beat, love, Hx-spam-relays-external:ESMTPA X-HELO: out2-smtp.messagingengine.com Received: from out2-smtp.messagingengine.com (HELO out2-smtp.messagingengine.com) (66.111.4.26) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 16 Jan 2017 14:49:17 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 39BF22097E; Mon, 16 Jan 2017 09:49:16 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Mon, 16 Jan 2017 09:49:16 -0500 X-ME-Sender: Received: from [192.168.1.102] (host86-173-196-32.range86-173.btcentralplus.com [86.173.196.32]) by mail.messagingengine.com (Postfix) with ESMTPA id CAFEA7E3B9; Mon, 16 Jan 2017 09:49:15 -0500 (EST) Subject: Re: WinCompose vs. Cygwin/X To: cygwin@cygwin.com References: <05386364-2022-02b5-9821-8cfbb59e6733@mscha.org> Cc: Michael Schaap From: Jon Turney Message-ID: Date: Mon, 16 Jan 2017 14:49: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 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2017-01/txt/msg00192.txt.bz2 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 >>> , >>> 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