From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from Ishtar.sc.tlinx.org (ishtar.tlinx.org [173.164.175.65]) by sourceware.org (Postfix) with ESMTPS id 43F05385803F for ; Sat, 10 Apr 2021 19:14:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 43F05385803F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tlinx.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=cygwin@tlinx.org Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id 13AJErgi007163; Sat, 10 Apr 2021 12:14:57 -0700 Message-ID: <6071F92E.5050802@tlinx.org> Date: Sat, 10 Apr 2021 12:14:54 -0700 From: L A Walsh User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Jon Turney CC: The Cygwin Mailing List Subject: Re: X11 blinking cursor in text window like 'gvim' - only halts if moved-over another X11-win References: <606CFC89.6030700@tlinx.org> <3a23e83c-670b-c599-b77b-18074dadf42e@dronecode.org.uk> In-Reply-To: <3a23e83c-670b-c599-b77b-18074dadf42e@dronecode.org.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Apr 2021 19:14:59 -0000 On 2021/04/09 07:41, Jon Turney wrote: > > I think so, yes. === That's fine, I guess I hadn't noticed it before -- had about 3-X and maybe 2 native and couldn't figure out why I occasionally had typing going to the wrong window when I realized I had been relying on the blinking for the active window...oi! > > See [1] et seq. for a discussion of what I think is the same problem, > where the Cygwin X server doesn't notify X windows of a focus loss when > the focus moves to a non-X window. > > Unfortunately, my attempts at fixing this just introduced more problems > (see [2],[3] et seq.), and so were reverted. === That's unfortunate. Well, I wasn't sure if it was new or old. At least its not some new problem. Sigh. Thanks for the backstory. > > [1] https://sourceware.org/legacy-ml/cygwin/2017-04/msg00168.html > [2] https://sourceware.org/legacy-ml/cygwin/2017-04/msg00278.html > [3] https://sourceware.org/pipermail/cygwin/2017-May/232564.html