add troubleshooting information about bash 2.05 not appending a / when

complete -o filenames is used
This commit is contained in:
ianmacd 2002-02-20 05:53:33 +00:00
parent b489ac4cff
commit b19e3d0992

15
README
View File

@ -1,4 +1,4 @@
$Id: README,v 1.2 2002/02/12 16:54:57 ianmacd Exp $ $Id: README,v 1.3 2002/02/20 06:53:33 ianmacd Exp $
INSTALLATION INSTALLATION
@ -42,11 +42,20 @@ If you get errors about 'complete' or 'compgen' not accepting the -g flag,
you are probably running bash 2.05 and should either apply the group completion you are probably running bash 2.05 and should either apply the group completion
patch, download a prepatched bash binary of 2.05, or upgrade to 2.05a or later. patch, download a prepatched bash binary of 2.05, or upgrade to 2.05a or later.
If you find that some commands, such as 'cd /usr<Tab>', end with a trailing
space instead of appending a /, you are probably running the base version of
bash 2.05, which suffers from a bug that causes the '-o filenames' option to
the complete built-in to be ignored. You can fix this by applying the following
the following official patch from the bash maintainer:
ftp://ftp.cwru.edu/pub/bash/bash-2.05-patches/bash205-006
If you get errors about 'complete' not accepting the -o flag, you are probably If you get errors about 'complete' not accepting the -o flag, you are probably
running bash 2.04. In this case, you should upgrade to bash 2.05a or later. running bash 2.04. In this case, you should upgrade to bash 2.05a or later.
Copies of the patches are prepatched versions of bash are available from Copies of the patches and prepatched versions of bash are available from:
my Web site at http://www.caliban.org/bash/
http://www.caliban.org/bash/
-- --
Ian Macdonald <ian@caliban.org> Ian Macdonald <ian@caliban.org>