Mail Archives: djgpp/2001/07/13/17:00:19
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
- Raw text -