Am 28.08.2025 um 07:31 schrieb Kevin Schnitzius via Cygwin:
On Wed, Aug 27, 2025 at 11:37 PM Thomas Wolff via Cygwin
<cygwin@cygwin.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?
No.
I am aware of the historic ^O flush function, even available on pre-Unix
operating systems (DEC TOPS).
That function would not explain the erratic behaviour seen with WSL.
"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 saw that patch. It is in no way what it claims, a "documentation" of
the setting.
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
