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