DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 57S5WbqY853500
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E1F0B3858C60
MIME-Version: 1.0
References: <1b1e8e7f-0ee9-41b8-931f-202af6704c4d AT towo DOT net>
In-Reply-To: <1b1e8e7f-0ee9-41b8-931f-202af6704c4d@towo.net>
Date: Thu, 28 Aug 2025 01:31:18 -0400
Message-ID: <CAJN=LAgh7qT9nL5KsH1Y98t8W9hSKyUu3AwpE4WiK8oReeMMEQ@mail.gmail.com>
Subject: Re: pty read loop losing data in wsl context
To: cygwin AT cygwin DOT com
From: Kevin Schnitzius via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Kevin Schnitzius <dont DOT know DOT at DOT all AT gmail DOT com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit

On Wed, Aug 27, 2025 at 11:37 PM Thomas Wolff via Cygwin
<cygwin AT cygwin DOT com> wrote:

> What’s the role of ^O in this puzzle? Does it trigger something in cygwin?
> Is there anything peculiar that would cause pty chunks not be recognised
> and then skipped in such a loop?

discard = ^O

       * discard CHAR
              CHAR will toggle discarding of output

Does a second ^O undo the problem?

"The equivalent of this is 'flush', but that was never documented
as an option (though was output with stty -a).  Therefore use
the more descriptive name, also generally used on BSD systems.
Note even though this setting seems ineffective on Linux, supporting
the setting is useful to allow terminal programs to receive
the default ^O character code."

https://lists.gnu.org/archive/html/coreutils/2015-01/msg00068.html

I really have no idea about how this is supposed to work...

Kevin

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple