Subject: Re: Bash bug wth read
From: [email-masked] (Peter Dalgaard BSA)

28 Jan 1997 14:40:22 -0800
Approved: [email-masked]
Distribution: cygnus
Message-ID: <[email-masked]>
References: <[email-masked]>
	<[email-masked]> <[email-masked]>
Original-To: Peter Dalgaard BSA <[email-masked]>
Original-Cc: [email-masked]
In-Reply-To: Peter Dalgaard BSA's message of 28 Jan 1997 10:59:51 +0100
X-Mailer: Gnus v5.2.40/Emacs 19.34
Original-Sender: [email-masked]

Peter Dalgaard BSA <[email-masked]> writes:

> What happens if you execute "bash < /dev/tty" and *then* ./script ?  

Well, I didn't have an obvious script around to try, but

bash < /dev/tty

followed by 

cat

gets rid of the annoying extra line at the top. Unfortunately, there
now seems to be no way to get OUT of cat! ^D, ^C, ^Z just print 
Got 4, Got 3, Got 26

What's with the keyboard-generated signals anyway? Stty seems to
mostly protest that it can't do things and even when it doesn't,
nothing happens. And I'm still no closer to figuring out why readline
strips composed characters. Anyone have a clue what to look for?

-- 
   O__  ---- Peter Dalgaard             Blegdamsvej 3  
  c/ /'_ --- Dept. of Biostatistics     2200 Cph. N   
 (*) \(*) -- University of Copenhagen   Denmark      Ph: (+45) 35327918
~~~~~~~~~~ - ([email-masked])             FAX: (+45) 35327907
-
For help on using this list, send a message to
"[email-masked]" with one line of text: "help".