From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) by sourceware.org (Postfix) with ESMTPS id 2B2FB3858403 for ; Wed, 15 Sep 2021 17:18:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2B2FB3858403 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=towo.net Authentication-Results: sourceware.org; spf=none smtp.mailfrom=towo.net Received: from [192.168.178.72] ([91.65.247.112]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1M1YxX-1mSTIY1Lyt-0033hU for ; Wed, 15 Sep 2021 19:18:49 +0200 Subject: Re: cygwin terminal window disrupts scroll-lock state To: cygwin@cygwin.com References: From: Thomas Wolff Message-ID: Date: Wed, 15 Sep 2021 19:18:50 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:AwmI1s8bWbEY1UGJo87ibPtKfnlhya/tMMjdO56Z0v+zGGAJ4DR DIguKYserAF+gmOEM680NzpqPr8yuX6puFI5PlukF0+SKur6GXrQE89X/MqmATyGCRqyVti /DA814UVKtB3csyKDEzFIILgXLjp6rYX2qDGOpBjZEW2Vu8Ew6AhZXQDlW1Cq2VHvfAJcez ozEMZ42c7dFprrnFKDSVg== X-UI-Out-Filterresults: notjunk:1;V03:K0:/DvpFjv8fSI=:X+KWWlWnFrKEkuyLxUPgjw bKqjfDua72BhPFbJulHp04NrsrF7jdUJlm0tjd4eISjJZQd+vurB1PjdYwRfCRv0JhVgRTpW+ 9FRxOmN71K7pWHN5c5YeA7LK6oPpz8Msp5H+xiR6AyFzocN7mFyWY6DvTDPJuhMor7A9iAfpB P9V/HmO1PAJmk4R8DVpAwHjL2wC7Rl6SVvZG4CaBc/JbxnmUem1oafkntrguC+ciQ9FKSVujE UoOx3xKd7r0CXR17YikYvSs24mLHV7lO3iUltNf1ATOcY8nqARSj/kFpp0J35lKQ9Dld1QPX6 Yxy6g/GSXOPZrf6A04c6ISleN0C/GJRr/6gTDgf+b07U1ssW6kGFogyFWWFS+toBV7dYB5njD 4awEtx8rGYau+43nRj3trE6Iu3YMwu5h1GgvNbtFGsWVYzZTrXN3mIgjDd1f5l6cg+p/aapiv Le/NaFwA1eRymwJr5cs6caSe1HFRRCAD7HK+QTtJsjzrmJI8izA3qcwHwBYfdC/vtoydlxPrE hIlJMEuO1sYiaJvjntSEup00Y8qfwoxHh1EsAhKWnP6EpH+hRy4/kZqMRhgmaGmE/rW72+G6L Uuvjo/2MnhAUu883l3TwbMA90C5A6Yrsot8ysav4IPLin4yiJdQAuEKgVYdmUhJWlaAtU7wxA YVEAWm6DYYXnv8zk87TZEPzLQss2wJIUPqQG65VLK4MLPFvgRTsJCNete9tEy2eklKd+8yL8u WUV1wG5LaqzoGVdHKFF+WUUM9SZmQVLoppbZ6Q== X-Spam-Status: No, score=-3.5 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: Wed, 15 Sep 2021 17:18:52 -0000 Am 15.09.2021 um 11:59 schrieb Eric Adams via Cygwin: > Hi, > > In the last few days, I have noticed a new behavior. Activating or > deactivating a Cygwin terminal window may change the state of my > keyboard's scroll-lock light. Keyboard LED management is a new feature as described in the manual page. The purpose is to keep the LEDs consistent with the state of the terminal window. > Inside a terminal window, the keyboard scroll-lock key may not change the corresponding light. If you assign a user-defined no-scroll or scroll-mode function to a key (regardless of whether it's the ScrollLock or another key), the ScrollLock will change accordingly. > What I have: > my startup icon command: C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico - > my shell: tcsh > my prompt: '%m:%c3 \!> ' > my OS: Windows 10 Home / 21H1 / 19043.1237 > my keyboard: CoolerMaster Devastator II (illuminated) > > If I activate a terminal window, the scroll-lock light may (or may > not) change state. If I press the scroll-lock key, the light may (or > may not) change state. It will be changed to the terminal state when the terminal window gets focus and restored to the system state when the terminal loses focus, as you noted below. > Holding the key down causes the light to flicker, and on releasing the key the final state may be either on or off. Auto-repeat may in fact confuse the state management, to be checked for a race condition. > Returning focus to a windows application seems to restore the > "desired" scroll-lock state. > > My observation is based on the use of the scroll-lock light to control the illumination of this keyboard. What is your use case and how do you control the LEDs? Anyway, if you do not wish mintty to manage the ScrollLock (or any) LED, try setting ManageLEDs=3 or ManageLEDs=0 Thomas > Thanks for your attention, > Eric Adams.