diff options
| author | ianmacd <> | 2002-02-20 05:53:33 +0000 |
|---|---|---|
| committer | ianmacd <> | 2002-02-20 05:53:33 +0000 |
| commit | b19e3d09929b88ab6684b1aa289dca9126fbe6e0 (patch) | |
| tree | 8592f7ff4200f7dedfaea16086bf32ffd0432bf4 /README | |
| parent | b489ac4cffcbf2e9c3bf6511df2e81ff35f9d3ad (diff) | |
| download | bash-completion-b19e3d09929b88ab6684b1aa289dca9126fbe6e0.tar.gz | |
add troubleshooting information about bash 2.05 not appending a / when
complete -o filenames is used
Diffstat (limited to 'README')
| -rw-r--r-- | README | 15 |
1 files changed, 12 insertions, 3 deletions
@@ -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 @@ -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 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 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 -my Web site at http://www.caliban.org/bash/ +Copies of the patches and prepatched versions of bash are available from: + + http://www.caliban.org/bash/ -- Ian Macdonald <ian@caliban.org> |