delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2000/06/29/11:59:34

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
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Thu, 29 Jun 2000 11:58:07 -0400
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: [ANNOUNCEMENT] Updated: ash-20000627
Message-ID: <20000629115806.B728@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com
References: <17B78BDF120BD411B70100500422FC6309E06F AT IIS000>
Mime-Version: 1.0
User-Agent: Mutt/1.2i
In-Reply-To: <17B78BDF120BD411B70100500422FC6309E06F@IIS000>; from Dautrevaux@microprocess.com on Thu, Jun 29, 2000 at 02:47:55PM +0200

On Thu, Jun 29, 2000 at 02:47:55PM +0200, Bernard Dautrevaux wrote:
>> Dave Arnold wrote:
>> > What is ASH? Is it the same as BASH?  I opened a bash shell 
>> on my win95
>> > install of cygwin and tried to find ash and couldn't find 
>> it anywhere?
>> > 
>> > /dAVe
>> 
>> No, Bash and Ash are two seperate shells. Bash could be described as
>> Ash on steroids. It is bigger and more complex, while Ash is small
>> and fast. Two different outlooks on the same kind of program.
>> 
>> > 
>> > >I've installed a new version of ash in 
>> sourceware:/cygwin/latest/ash.
>> > >
>> > >Changes:
>> > >
>> > >- When evaluating stdout of backquote commands, it's read in
>> > >  textmode to handle native windows commands in backquotes as
>> > >  well.
>> 
>> I have not made this change to Bash, as this is controlled by 
>> the CYGWIN
>> environment variable setting to binmode to keep the carriage 
>> returns or
>> to nobinmode to remove them. This is of course an over-simplification
>> of the actual reason, but I hope I have gotten my point across. If
>> you, the user, want the stripping of the carriage returns, then it is
>> YOUR responsibility to set the variable accordingly. See Earnie Boyd's
>> site for more information, as Earnie has a much better way with words
>> than I do.
>> 
>> Comments, flames, chocolate-chip cookies are all appreciated.
>> ^^^^^^^^
>
>Just one: back-quote substitution is used in TEXT context: it replace some
>TEXT by some other TEXT; arguing it may be BINARY data is quite obscure to
>me :-)
>
>For me Corinna is perfectly correct by reading the output from the command
>substitution in text mode regardless of the CYGWIN setting.

I agree with this.  Obviously, we could have come to the same conclusion with
ash.  It was also controlled by CYGWIN=binmode but it doesn't make any sense
to me that back quoted text should ever have a CR in it.

I think that bash should also use textmode in this case.

cgf

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019