[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange behavior in command completion
From: |
Fabio Brugnara |
Subject: |
Re: Strange behavior in command completion |
Date: |
Thu, 25 Jul 2002 08:36:37 +0200 |
User-agent: |
Mutt/1.2.5.1i |
On Wed, Jul 24, 2002 at 12:45:04PM -0400, Chet Ramey wrote:
> > Machine Type: i686-pc-linux-gnu
> >
> > Bash Version: 2.05b
> > Patch Level: 0
> > Release Status: release
> >
> > Description:
> >
> > When using readline completion for commands, sometimes completion
> > stops too early, ending a directory name with a space.
>
> Try this patch, and see if it does the right thing:
>
> *** ../bash-2.05b/bashline.c Tue May 7 15:52:42 2002
> --- bashline.c Wed Jul 24 12:22:57 2002
> ***************
> *** 1053,1057 ****
> --- 1053,1061 ----
> if (matches == (char **)NULL)
> rl_ignore_some_completions_function = bash_ignore_filenames;
> + #if 0
> else if (matches[1] == 0 && *matches[0] != '/')
> + #else
> + else if (matches[1] == 0 && absolute_pathname (matches[0]) == 0)
> + #endif
> /* Turn off rl_filename_completion_desired so readline doesn't
> append a slash if there is a directory with the same name
>
> --
It works with paths starting with ., but it still stops prematurely
with references starting with ~, such as ~/bin.
best regards,
Fabio Brugnara