From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ericbadams@gmail.com>
Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com
 [IPv6:2607:f8b0:4864:20::f30])
 by sourceware.org (Postfix) with ESMTPS id 8A8503858439
 for <cygwin@cygwin.com>; Wed, 15 Sep 2021 09:59:29 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8A8503858439
Received: by mail-qv1-xf30.google.com with SMTP id r18so1499166qvy.8
 for <cygwin@cygwin.com>; Wed, 15 Sep 2021 02:59:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=h4Y1iNnh/rVit1ubKsZI9wRYB4IfmxGGo+mp7k2yAXQ=;
 b=I/sCL02MPUtMNTk71ek168Ir1G3Lh/p3JJbfcqF9eksZtmp/SVwjPCiTNDMLtUWxLv
 kVDFKhLyG0aJp54JGusBj42bZaa1/kM90WjltkUXiPSUHqbtq5jsYctTXO1rU/W9XRJ1
 r88kCZrlujLXnxa3PBxPTbeBG6mRI1ah7fmoeamnpicfuDIDpanP5VWv7rZQdpJhPaGA
 3WV1+9qGrWLfrcJ2/c2VkeckPUkG2RsJWLpF5Kd8kTkmum7893PYgZjzlJd10/jOlZBC
 5+8zSNakUKgj92N2DOfXGO1ttOyvoz0ev/ukbho1E/RSS7nriRVXraTDGtKzyBCVjN+a
 h4hA==
X-Gm-Message-State: AOAM532bbq4OLUxPc7jlnzuTePcpcXaAxo5ZOL7RF23NjvW2KJsK5HxQ
 8fjUqXcuWgCFHukX5co7s+uTlvV4EjPOB49BJkCxL6oKpw3tuFU6
X-Google-Smtp-Source: ABdhPJw7TlGEpb7280dJajC7wU/omNWAh08f26rB+XaGTT28e3jDhwO/HZdXe/GVkHt7p0O51ZVHSOymAL2TiSz+YJU=
X-Received: by 2002:a05:6214:13a3:: with SMTP id
 h3mr9794435qvz.26.1631699968707; 
 Wed, 15 Sep 2021 02:59:28 -0700 (PDT)
MIME-Version: 1.0
From: Eric Adams <ericbadams@gmail.com>
Date: Wed, 15 Sep 2021 04:59:02 -0500
Message-ID: <CAA=0bENP5bMkV5gc_au0BUpPrHGGnKwvRZ3O7erKbQQELNWw0g@mail.gmail.com>
Subject: cygwin terminal window disrupts scroll-lock state
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=2.3 required=5.0 tests=BAYES_50, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Level: **
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 <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2021 09:59:30 -0000

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. Inside a terminal window, the keyboard
scroll-lock key may not change the corresponding light.

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. Holding the key down causes the light to
flicker, and on releasing the key the final state may be either on or
off. 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.

Thanks for your attention,
Eric Adams.