bug-readline
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-readline] Key sequence initial prefix of another


From: Andre Majorel
Subject: Re: [Bug-readline] Key sequence initial prefix of another
Date: Sun, 7 Nov 2010 12:08:55 +0100
User-agent: Mutt/1.5.20 (2009-06-14)

On 2010-11-06 16:28 -0400, Chet Ramey wrote:
> On 10/22/10 3:56 AM, Andre Majorel wrote:
> > Suppose you have readline bindings of different lengths with the
> > same stem, E.G.
> > 
> >   "\eg":  " | grep "
> >   "\egi": " | grep -i "
> > 
> > To get
> > 
> >   ls | grep 12
> > 
> > you might type "ls[esc]g12" but you'll get
> > 
> >   ls1 | grep 2
> > 
> > Is this by design ?
> 
> You don't say which version of readline you're using, but I don't get
> this behavior on readline-6.0 (from bash-4.0) or readline-6.1 (from
> bash-4.1).  Both bash versions had all patches applied.

Thanks for looking. It occurs with Debian libreadline6 6.0-5 and
6.1-3.

I've tried starting bash with INPUTRC pointing to a file
containing only

"\eg":  " | grep "
"\egi": " | grep -i "

Same behaviour, so it seems it's not something else in my
inputrc triggering the bug.

A look at ftp://ftp.debian.org/debian/pool/main/r/readline6/rea
dline6_6.1-3.debian.tar.gz suggests that they have included all
available patches (readline61-001.diff and -002). They have a
few patches of their own but nothing likely to have the effect
I'm seeing.

Any suggestion as to what I could try next ?

-- 
André Majorel http://www.teaser.fr/~amajorel/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]