diff options
| author | ianmacd <> | 2002-06-25 14:29:41 +0000 |
|---|---|---|
| committer | ianmacd <> | 2002-06-25 14:29:41 +0000 |
| commit | d09b63e2e77035d787a81659cf0ba88a79788057 (patch) | |
| tree | 3d0883941307efcc055ec208ceab907dca07ab5c /README | |
| parent | 12bded6a0ff613d1ad7b0e34dceb572b405ae0b1 (diff) | |
| download | bash-completion-d09b63e2e77035d787a81659cf0ba88a79788057.tar.gz | |
- corrections to tar comments
Diffstat (limited to 'README')
| -rw-r--r-- | README | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -1,4 +1,4 @@ -$Id: README,v 1.13 2002/06/25 16:15:52 ianmacd Exp $ +$Id: README,v 1.14 2002/06/25 16:29:41 ianmacd Exp $ INSTALLATION @@ -143,13 +143,14 @@ A. It's a choice I had to make. bash's programmable completion is limited in how it handles the list of possible completions it returns. Because the paths returned from within the tar file are likely not existing - files on the file system, '-o filenames' must be passed to the complete + paths on the file system, '-o dirnames' must be passed to the complete built-in to make it treat them as such. However, then bash will append a space when completing on directories during pathname completion to the tar files themselves. It's more important to have proper completion of paths to tar files than - it is to have completion for their contents, so this sacrifice was made. + it is to have completion for their contents, so this sacrifice was made + and '-o filenames' is used with complete instead. If you would rather have correct path completion for tar file contents, define $COMP_TAR_INTERNAL_PATHS *before* sourcing bash_completion. |