Date: Tue, 3 Dec 1996 08:38:25 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Jerzy Witkowski <Jerzy DOT Witkowski AT ii DOT uni DOT wroc DOT pl>
cc: djgpp AT delorie DOT com
Subject: Re: Bug in bash.exe - inline input data
In-Reply-To: <x6ral9w6hq.fsf@dadzbog.ii.uni.wroc.pl>
Message-ID: <Pine.SUN.3.91.961203083414.3181G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


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?

> BTW, on my computer normal PC arrow keys didn't work in bash (it
> seems every one of them generates `C-@' only).

`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).