DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5B2E93851C0C
To: cygwin@cygwin.com
Subject: bug report: tty/termios flags weirdness
Message-ID: <d5493d27-ba72-7394-6d3a-5d164de41da4@glup.org>
Date: Sat, 14 Nov 2020 22:14:10 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
 Gecko/20100101 Thunderbird/78.4.3
MIME-Version: 1.0
Content-Language: en-US
From: john hood via Cygwin <cygwin@cygwin.com>
Reply-To: john hood <cgull@glup.org>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces@cygwin.com>
Content-Transfer-Encoding: 8bit

After thrashing with my own bugs for a while, I think I've found a minor
bug in Cygwin's tty/termios handling-- seen in 3.1.7 on Windows 10
20H2.  Among other things, this causes tmux to fail on non-pty sessions.

STC:

Start Cygwin in conhost or Windows Terminal.

Execute 'stty -isig'

You will probably get an error message 

stty: 'standard input': unable to perform all requested operations

Repeat this test in mintty (or other pty-using sessions, probably)

You will probably not get this error message.

The stty error arises because stty does tcgetattr() after doing
tcsetattr(), and expects the termios struct it reads to be the same as
the one it wrote.  I haven't looked at tmux.

This isn't a big issue for me-- I was doing 'stty raw' which unsets this
flag, but I only needed raw output, so 'stty -opost' was the workaround.

regards,

  --jh


--
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