Date: Tue, 3 Dec 1996 10:12:04 +0100 (MET) Organization: University of Wroclaw, Institute of Computer Science Reply-To: Message-Id: <199612030912.KAA20446@ii.uni.wroc.pl> From: Jerzy Witkowski To: Eli Zaretskii CC: djgpp AT delorie DOT com Subject: Re: Bug in bash.exe - inline input data In-Reply-To: References: Eli Zaretskii writes: > On 2 Dec 1996, Jerzy Witkowski wrote: > > > ============================== result from DJGPP `awk' > > awk: cmd. line:2: fatal: error reading input file `stdin': > > Permission denied (EACCES) > > ============================== > > Would you care to tell how did you invoke `awk' to get the above > problem? awk '{ print $0 }' << end_of_file > out_file inline input file... end_of_file I have just checked it on another computer (with COMMAND.COM, not NDOS.COM) and there are two differences: - error shows for *every* input (not only for >= 512 B); - error message is 'awk: cmd. line:2: fatal: can't stat fd 0 (Bad file descriptor (EBADF))'. > `bash' uses the `readline' library to read the keystrokes, and the DJGPP > port of that library doesn't support arrows. Use the Emacs-style > cursor-motion keys instead (^P for previous line, ^N for next line, ^F > for forward character, ^B for backward character, etc.). Better still, > grab the sources and teach `readline' about editing keys (as far as I > remember, it's a simple matter of using a different library function to > read the keyboard). Yes, I know, I just hoped it was done already :-). I think I'll try. -- Jerzy Witkowski o o University of Wroclaw, Institute of Computer Science /| | |/| Przesmyckiego 20, PL-51151 Wroclaw |/| | | room: 11, phone: 0048 71 3247360 /| |/^\| | phone/fax office secretary: 0048 71 3251271 <__|