Subject: bash extra newline bug?
From: [email-masked] (Mumit Khan)

9 Apr 1997 21:14:41 -0700
Approved: [email-masked]
Distribution: cygnus
Message-ID: <[email-masked]>
Original-To: [email-masked]
Original-Sender: [email-masked]

Does anybody have a patch for the extra newline that bash seems to create
when exec/sourc'ing programs/shell script?

Didn't find any info on it on the various Web sites related to gnu-win32.

eg., the read statement fails in the following script (always gets an
empty line):

### CUT FROM HERE
#
#! /bin/sh

echo_n="-n"; echo_c=""
echo $echo_n "Is this correct [y/N]? " $echo_c

read ans

echo "Answer is = $ans"

case "$ans" in
  y | Y | yes | YES)
  ;;
  *)
    exit 1
  ;;
esac

exit 0
# 
### TO HERE

Funny thing is that if I run the script from COMMAND.COM, it works *every
other* time!
    
Regards,
Mumit -- [email-masked]
http://www.xraylith.wisc.edu/~khan/

-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".