From: pd AT kubism DOT ku DOT dk (Peter Dalgaard BSA) Subject: Re: Bash bug wth read 28 Jan 1997 14:40:22 -0800 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: References: <01BC0B86 DOT D4EA9D80 AT wayned DOT sc DOT scruznet DOT com> <32ECF113 DOT 62D8 AT chromatic DOT com> Original-To: Peter Dalgaard BSA Original-Cc: gnu-win32 AT cygnus DOT com 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: owner-gnu-win32 AT cygnus DOT com Peter Dalgaard BSA 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 ~~~~~~~~~~ - (p DOT dalgaard AT biostat DOT ku DOT dk) FAX: (+45) 35327907 - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".