Re: Readline sometimes doesn't autocomplete until the next disambiguation

[Chet Ramey]

On 12/29/22 1:01 PM, Martin Castillo wrote:
> Hi,
>
> Am 27.12.22 um 20:36 schrieb Chet Ramey:
> > On 12/25/22 10:22 AM, Martin Castillo wrote:
> > > Hi,
> > >
> > > consider this folder:
> > >
> > > $ mkdir -p "a b/c d e"
> > > $ touch a\ b/c\ d\ e/10._{f,g}
> > >
> > > typing
> > > $ ls a\ b/c\ d\ e/<TAB> or
> > > $ ls a\ b/c\ d\ e/1<TAB>
> > > changes the line to
> > > $ ls a\ b/c\ d\ e/10._
> > > as it should, but typing
> > > $ ls a\ b/c\ d\ e/10<TAB>  or
> > > $ ls a\ b/c\ d\ e/10.<TAB>
> > > does not add further characters to the input line.
> >
> > I can't reproduce this using bash-5.1 or bash-5.2.
>
> I'm sorry. you need to add
> set show-all-if-ambiguous on
> in ~/.inputrc

OK, I see the issue now. It happens when the text from the line buffer
(quoted) is compared to the common prefix of the matches (unquoted), and
the quoting makes the former appear longer than the latter, so the code
assumes that the match doesn't add any characters to the word.  I'll
fix it in the next bash devel branch push.

Chet

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/