Setting CYGWIN=tty in an already running shell leads to hidden output
Volker Quetschke
quetschke@scytek.de
Sat Dec 9 02:45:00 GMT 2006
It's a little more complicated than the subject suggests, the output
vanishes after the first command in a new bash. Have a look at the
following recipe:
1. Start cygwin.bat (no prior setting of the CYGWIN environment
variable)
See the transcript of an example session:
quetschke@Turion ~
$ echo $CYGWIN
quetschke@Turion ~
$ export CYGWIN=tty
quetschke@Turion ~
$ bash
quetschke@Turion ~
$ blah
bash: blah: command not found [1]
quetschke@Turion ~
$ bash: blah: command not found [2]
quetschke@Turion ~
$ bash: blu: command not found [3]
quetschke@Turion ~
$
At [1] blah is typed and still echoed but at [2] it is not echoed
anymore and at [2] blu was typed that was also not echoed anymore.
cygcheck output follows.
Volker
P.S.: In case someone wonders, I was hunting a problem where CTRL-c
is only belatedly delivered to a cygwin process if tty is not set
to CYGWIN but it works as expected if CYGWIN=tty is set and found
this effect while trying.
--
PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cygcheck.log
URL: <http://cygwin.com/pipermail/cygwin/attachments/20061209/ef032df9/attachment.log>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 248 bytes
Desc: OpenPGP digital signature
URL: <http://cygwin.com/pipermail/cygwin/attachments/20061209/ef032df9/attachment.sig>
More information about the Cygwin
mailing list