This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: bash 2.05b-7 and command line tab completion
- From: "Harig, Mark A." <maharig at idirect dot net>
- To: "Eric Blake" <ebb9 at email dot byu dot edu>,<cygwin at cygwin dot com>
- Date: Thu, 7 Nov 2002 11:23:20 -0500
- Subject: RE: bash 2.05b-7 and command line tab completion
I can't tell whether this bug (tab-completion
adding a space when it is used for the first
word after the prompt) is Cygwin-specific, or
if it was added with bash 2.05. My two versions
of bash running on Linux are 2.04. Neither of
them have this bug. Does someone have another
(non-Cygwin) bash 2.05 that can test this
behavior?
> -----Original Message-----
> From: Eric Blake [mailto:ebb9@email.byu.edu]
> Sent: Thursday, November 07, 2002 10:25 AM
> To: cygwin@cygwin.com
> Subject: bash 2.05b-7 and command line tab completion
>
>
> I'm still having problems with tab completion in the latest bash:
>
> $ bash --version
> GNU bash, version 2.05b.0(7)-release (i686-pc-cygwin)
> Copyright (C) 2002 Free Software Foundation, Inc.
> $ ll ~/jacks/jacks # I typed ll ~/ja[TAB]jacks
> -rwxr-xr-x 1 eblake unknown 558 Jul 24 18:33 jacks*
> $ ~/jacks jacks # I typed ~/ja[TAB]jacks
>
> I expected to get ~/jacks/jacks both times, but the bash is
> inserting a
> space after ~/directory when it is the first (but not subsequent)
> command line word. However, /h[TAB]e[TAB]ja[TAB]jacks now
> works, giving
> /home/eblake/jacks/jacks (and it hasn't always done so in
> prior versions
> of bash). So whatever was fixed to make /-based tab completion work
> needs to also apply to ~-based tab completion.
>
> --
> This signature intentionally left boring.
>
> Eric Blake ebb9@email.byu.edu
> BYU student, free software programmer
>
>
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/