This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: 1.1.8: the read command in bash does not behaive the same as in ksh
- To: "'sdelrio at home dot com'" <sdelrio at home dot com>, cygwin at cygwin dot com
- Subject: RE: 1.1.8: the read command in bash does not behaive the same as in ksh
- From: Neil Lunn <neillunn at gunz dot com dot au>
- Date: Tue, 24 Apr 2001 17:00:32 +1000
read is a built-in, you cannot pipe to it.
-----Original Message-----
From: Sergio Del Rio [mailto:sdelrio@home.com]
Sent: Tuesday, April 24, 2001 4:26 PM
To: cygwin@cygwin.com
Subject: 1.1.8: the read command in bash does not behaive the same as in ksh
This was encountered with cygwin v1.1.8 under Windows 2000 Professional.
The following script executes fine on other unix systems but not with cygwin
and I was wondering how to get around this problem:
echo one two three | read v1 v2 v3
echo "v1 = ${v1}"
echo "v2 = ${v2}"
echo "v3 = ${v3}"
It seems that the variables are not set at all when this is done with
cygwin.
I have this kind of code in many places and would really appreciate an
answer.
Thanks!
Regards,
Sergio Del Rio
Templates 4 Business Inc.
Cell: (604) 788-3604
Fax: (604) 582-7877
__________________________________________________________________________
Please Note :
Only the intended recipient is authorised to access or use this e-mail. If
you are not the intended recipient,
please delete this e-mail and notify the sender immediately. The contents
of this e-mail are the writer's
opinion and are not necessarily endorsed by the Gunz Companies unless
expressly stated.
We use virus scanning software but exclude all liability for viruses or
similar in any attachment.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple