From: cgf@bbc.com (Christopher Faylor) Subject: Re: Problem with rcs... 11 Mar 1998 20:16:42 -0800 Message-ID: References: <19980310185249.2132.qmail@hotmail.com> Reply-To: cgf@bbc.com To: gnu-win32@cygnus.com In article <19980310185249.2132.qmail@hotmail.com>, Earnie Boyd wrote: >Goto Christopher Faylor's page and get the cygwinb19.zip file. He has a >new version which may help. Before starting bash try setting >CYGWIN32=notty. If that doesn't work then exit bash set CYGWIN32=tty. >If that doesn't work, report it to Christopher. > >NOTE: You cannot change the [no]tty value in the CYGWIN32 value after >bash has started. This could cause crashes and core dumps. I hope this isn't the case. I might have inferred that in previous email but what I meant was that under B18 you could get really strange behavior if you unset CYGWIN_TTY. Under B19, you can unset it, but if your shell is using a tty for stdin/stdout/stderr, etc., then all of its subprocesses will as well. -- http://www.bbc.com/ cgf@bbc.com "Strange how unreal VMS=>UNIX Solutions Boston Business Computing the real can be." - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".