From: HARY <Hary AT address DOT is DOT invalid>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bash-crash and other '_inputrc' problems.
Date: 13 Jul 2001 20:49:51 GMT
Organization: Wielki samotnik w swoim zamku.
Lines: 39
Message-ID: <slrn.pl.9kt442.c6.Hary@pingwin.domciu.net>
References: <slrn DOT pl DOT 9kkjeu DOT f7 DOT Hary AT pingwin DOT domciu DOT net> <Pine DOT SUN DOT 3 DOT 91 DOT 1010710111956 DOT 18978O-100000 AT is>
NNTP-Posting-Host: pg23.wroclaw.cvx.ppp.tpnet.pl
X-Trace: news.tpi.pl 995057391 23260 217.99.225.23 (13 Jul 2001 20:49:51 GMT)
X-Complaints-To: usenet AT tpi DOT pl
NNTP-Posting-Date: 13 Jul 2001 20:49:51 GMT
User-Agent:  slrn/0.9.7.0 (pl-1.1.1) (Linux)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> On 10 Jul 2001, HARY wrote:
> > I'm not sure if the way I'm trying to get national characters is legal
> > (is it?), but I think that bash should survive even nonsense
> > configuraton files.
> > Moreover, there are some example definitions in sample '_inputrc', that
> > don't work as expected:
> > "\e[0XA": "Function Key 1"
> > 'F1' key doesn't display string, it displays "A" and beeps.
> Try adding this to your _inputrc:
>   set meta-flag on
>   set convert-meta off
>   set output-meta on

Thank you.

I was so impressed (by effects that I've described previously) that I even
didn't try this before posting here.

Ok, this solves 17/18 of my problem. One character (0x0e) still cannot be
entered - even using Alt+keypad technique. Function that handles bash's
keyboard input apparently doesn't "know" that this code is not always
prefix.

There are other weird things with bash's input handling.
For example, including in _inputrc:

"\245":"anything" 

causes bash to exit when this character is entered, but

"\244":"anything"

is ok.

As to function keys definitions: they were wrong in sample '_inputrc'
for version 2.03 (corrected in 2.04). F1 should be "\e[0A" and so on.

  HARY