Re: [rfc] Completion tests failing

[Daniel Jacobowitz <drow@mvista.com>]

On Thu, Sep 27, 2001 at 09:08:14PM +0200, Eli Zaretskii wrote:
> > Date: Thu, 27 Sep 2001 13:00:26 -0400
> > From: Daniel Jacobowitz <drow@mvista.com>
> > 
> > On Thu, Sep 27, 2001 at 05:37:10PM +0200, Eli Zaretskii wrote:
> > > > Date: Thu, 27 Sep 2001 10:34:01 -0400
> > > > From: Daniel Jacobowitz <drow@mvista.com>
> > > > 
> > > > I wanted to get a name that I knew would complete unambiguously, so I
> > > > tried using '"break.', which ought to complete to '"break.c"'.  It
> > > > completes instead to '"break.c ' - trailing space, no trailing quote.
> > > 
> > > Try this twice, one after the other, and you will see that only the
> > > first time fails.  The second and all the successive times will
> > > complete to `"break.c"'.
> > 
> > What do you mean by twice?  I can't get `"break.' to complete to `"break.c"'
> > at all, no matter what I try.
> 
> Sorry, I didn't realize the importance of starting with "break.,
> including the period.  Anything else correctly completes to "break.c".

(on the first try, best I can see)

> The reason for this is that Readline only passes our completion
> function the part after the period, so we never see the "break part.

Well, that's not right either.  It completes unambiguously to break.c.
Oh, on the other hand I see that text contains the whole string and
word contains only \0.  This is definitely a guts-of-readline problem,
as readline thinks that the "." is a word separator, which is not
precisely correct.  Oh, well.  XFAIL for now, and we can poke at this
some more later.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer