Re: bash CRLF problems (I have read the recent announcement)

2006-12-06 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Dave Korn on 12/6/2006 4:54 PM: > > Actually, there was just /one/ more thing... I don't know if it's equally > as cross-platform as 'read', but it is defined by POSIX, and you kept on > mentioning that you can't use d2u because it's n

RE: bash CRLF problems (I have read the recent announcement)

2006-12-06 Thread Dave Korn
On 06 December 2006 23:44, Kevin Layer wrote: > Eric Blake <[EMAIL PROTECTED]> wrote: Kevin, please snip raw email addys when you reply - it gets people spammed. http://cygwin.com/acronyms#PCYMTNQREAIYR for more. >>> read version < foo1.out > > I prefer this to the echo -n, because the latte

Re: bash CRLF problems (I have read the recent announcement)

2006-12-06 Thread Kevin Layer
Eric Blake <[EMAIL PROTECTED]> wrote: >> read version < foo1.out I prefer this to the echo -n, because the latter isn't supported on all the platforms I run on (aix, for one). Thanks for the help. You guys rock. Kevin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem

Re: bash CRLF problems (I have read the recent announcement)

2006-12-05 Thread Kevin Layer
Mark Fisher <[EMAIL PROTECTED]> wrote: >> if you change the echo's to "echo -n" you don't get the ^M chars, as >> it surpresses the CR in the output. >> is this possible on the "real" scripts you talk about, or is the >> version generating script/app not changeable? The only restriction is that i

Re: bash CRLF problems (I have read the recent announcement)

2006-12-05 Thread Mark Fisher
On 12/5/06, Kevin Layer wrote: Larry Hall (Cygwin) wrote: >> > version=`cat foo1.out` >> > ... >> Time to adjust your expectations. ;-) Text mounts write CRNL as EOLs >> for all files that are not explicitly opened as binary (or text for >> that matter). Text mounts remove the CR from EOLs r

Re: bash CRLF problems (I have read the recent announcement)

2006-12-04 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Kevin Layer on 12/4/2006 3:59 PM: > I'm really perplexed by the following behavior: > > [EMAIL PROTECTED] ~ > $ cat -v foo1.sh > echo 8010 > foo1.out > > [EMAIL PROTECTED] ~ > $ cat -v foo2.sh > sh foo1.sh > version=`cat foo1.out` The r

RE: bash CRLF problems (I have read the recent announcement)

2006-12-04 Thread Wilks, Dan
Kevin Layer wrote: > I'm really perplexed by the following behavior: > > [EMAIL PROTECTED] ~ > $ cat -v foo1.sh > echo 8010 > foo1.out > > [EMAIL PROTECTED] ~ > $ cat -v foo2.sh > sh foo1.sh > version=`cat foo1.out` > echo ${version}.bar > foo2.out > cat -v foo2.out > > [EMAIL PROTECTED] ~ > $ sh f

Re: bash CRLF problems (I have read the recent announcement)

2006-12-04 Thread Kevin Layer
Larry Hall (Cygwin) <[EMAIL PROTECTED]> wrote: >> > version=`cat foo1.out` >> > ... >> Time to adjust your expectations. ;-) Text mounts write CRNL as EOLs >> for all files that are not explicitly opened as binary (or text for >> that matter). Text mounts remove the CR from EOLs read from files

Re: bash CRLF problems (I have read the recent announcement)

2006-12-04 Thread Larry Hall (Cygwin)
Kevin Layer wrote: I'm really perplexed by the following behavior: [EMAIL PROTECTED] ~ $ cat -v foo1.sh echo 8010 > foo1.out [EMAIL PROTECTED] ~ $ cat -v foo2.sh sh foo1.sh version=`cat foo1.out` echo ${version}.bar > foo2.out cat -v foo2.out [EMAIL PROTECTED] ~ $ sh foo2.sh 8010^M.bar^M [EMA

bash CRLF problems (I have read the recent announcement)

2006-12-04 Thread Kevin Layer
I'm really perplexed by the following behavior: [EMAIL PROTECTED] ~ $ cat -v foo1.sh echo 8010 > foo1.out [EMAIL PROTECTED] ~ $ cat -v foo2.sh sh foo1.sh version=`cat foo1.out` echo ${version}.bar > foo2.out cat -v foo2.out [EMAIL PROTECTED] ~ $ sh foo2.sh 8010^M.bar^M [EMAIL PROTECTED] ~ $ mou