Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <38CDD1EF.5650B3C@ece.gatech.edu>
Date: Tue, 14 Mar 2000 00:45:19 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Subshells don't respect CYGWIN settings with latest snapshots?
References: <38CD7EEA DOT 1FC69BE7 AT ece DOT gatech DOT edu> <20000313204437 DOT C22468 AT cygnus DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Chris Faylor wrote:
> 
> I'm sorry to say that I can't duplicate this behavior.  Maybe I just
> don't have a proper tar file or maybe my version of bash works differently.
> 
> I did check the "binmode" setting of a bash that was running in an rxvt
> invoked from another bash and the the cygwin=binmode setting was propagated.
> 
> cgf
> 

Well, that's what confused me. The cygwin=binmode setting was
propagated, but not *respected* in the child shell. 

However, your hint gave me the answer. It was my version of bash; I had
compiled 2.03.0(2) and was using that. When I reverted to 2.02.1(2)
[from the snapshots, I think] it worked. Are there any special
configuration settings I should choose when compiling bash?

--Chuck


> On Mon, Mar 13, 2000 at 06:51:06PM -0500, Charles Wilson wrote:
> >(Sorry if this is a duplicate; my regular ISP is on the ORBS list right
> >now...sigh...and I'm not sure if the first one made it)
> >
> >If I try to unpack a .tar.gz file with 'CYGWIN=nobinmode ntea tty' using
> >a pipe, I get an error -- this is the expected behavior (if the
> >tar-stream has binary characters..?).
> >
> >/usr/local/src/redhat/SOURCES/tmp > gzip -cd DelimMatch-1.04.tar.gz |
> >tar xf -
> >tar: Skipping to next file header
> >tar: Archive - EOF not on block boundary
> >tar: Error is not recoverable: exiting now
> >
> >However, if my global environment settings contain 'CYGWIN=binmode ntea
> >tty', then the first rxvt/bash window I open works thusly:
> >
> >/usr/local/src/redhat/SOURCES/tmp > echo $CYGWIN
> >tty ntea binmode
> >/usr/local/src/redhat/SOURCES/tmp > gzip -cd DelimMatch-1.04.tar.gz |
> >tar xvf -
> >DelimMatch-1.04/
> >DelimMatch-1.04/DelimMatch.pm
> >DelimMatch-1.04/Makefile.PL
> >DelimMatch-1.04/MANIFEST
> >DelimMatch-1.04/README
> >DelimMatch-1.04/test.pl
> >
> >Then, I start a subshell: in the first rxvt/bash window, I execute: rxvt
> >-e bash &. In the new bash window:
> >
> >/usr/local/src/redhat/SOURCES/tmp > echo $CYGWIN
> >tty ntea binmode
> >/usr/local/src/redhat/SOURCES/tmp >  gzip -cd DelimMatch-1.04.tar.gz |
> >tar xvf -
> >DelimMatch-1.04/
> >DelimMatch-1.04/DelimMatch.pm
> >tar: Skipping to next file header
> >tar: Archive - EOF not on block boundary
> >tar: Error is not recoverable: exiting now
> >
> >I see this behavior with the 20000311, 20000306, 20000228, 20000131,
> >20000106, and 19991124 snapshots. What's going on, anyone got a clue?
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com