diff options
| author | ianmacd <> | 2006-03-02 00:13:46 +0000 |
|---|---|---|
| committer | ianmacd <> | 2006-03-02 00:13:46 +0000 |
| commit | bada11acc6f0f49be8d1732e724029444b421a69 (patch) | |
| tree | 985a282d4b9d2bcfe0752c638bc0eeed5e368f2f /README | |
| parent | 9855305cda2940555d4d26a49e91bb5764090def (diff) | |
| download | bash-completion-bada11acc6f0f49be8d1732e724029444b421a69.tar.gz | |
Add a section about POSIX quoting issue in bash 3.1.
Correct URL to a previous patch for bash 2.05b.
Diffstat (limited to 'README')
| -rw-r--r-- | README | 37 |
1 files changed, 34 insertions, 3 deletions
@@ -1,4 +1,4 @@ -$Id: README,v 1.26 2006/02/25 14:41:11 ianmacd Exp $ +$Id: README,v 1.27 2006/03/02 01:13:46 ianmacd Exp $ INSTALLATION @@ -77,7 +77,7 @@ base version of bash 2.05, which suffers from a bug that causes the fix this by applying the following official patch from the bash maintainer: - ftp://ftp.cwru.edu/pub/bash/bash-2.05-patches/bash205-006 + ftp://ftp.gnu.org/gnu/bash/bash-2.05b-patches/bash205b-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 @@ -144,6 +144,36 @@ function used by mutt completion, where the function calls itself recursively. This seems to confuse bash and it issues spurious warnings if 'nounset' is set. +V. + +After upgrading to bash 3.1, you may notice that completing on certain +commands now fails with a message something like this: + + sed: -e expression #1, char 20: unterminated `s' command + +The reason for this is that bash 3.1 contains the following, +innocent-looking bug fix (from bash's CHANGES file): + + t. Fixed a bug that caused the expanded value of a $'...' string + to be incorrectly re-quoted if it occurred within a + double-quoted ${...} parameter expansion. + +Unfortunately, this also had the side effect of causing single quotes +to be stripped from $'...' strings inside double-quoted command +substitutions. Confused? + +Efforts have been made to work around this issue in the bash +completion code as of the 20060301 release. All previous versions are +vulnerable to the problem. However, it's possible that, even in the +20060301 release and later, affected code remains. + +The issue has now been officially recognised as a regression in the +bash 3.1 release and is fixed by official patch 11. If you encounter +problems of this nature, please apply the patch below to your copy of +bash: + + ftp://ftp.gnu.org/gnu/bash/bash-3.1-patches/bash31-011 + FAQ --- @@ -445,4 +475,5 @@ guidelines in mind: send it to me. -- -Ian Macdonald <ian@caliban.org> +Ian Macdonald +ian@caliban.org |