csonto/bash-completion
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

- corrections to tar comments

Browse Source
This commit is contained in:
ianmacd 2002-06-25 14:29:41 +00:00
parent 12bded6a0f
commit d09b63e2e7
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README
View File

@ -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 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. how it handles the list of possible completions it returns.
Because the paths returned from within the tar file are likely not existing 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 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 space when completing on directories during pathname completion to the tar
files themselves. files themselves.
It's more important to have proper completion of paths to tar files than 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, If you would rather have correct path completion for tar file contents,
define $COMP_TAR_INTERNAL_PATHS *before* sourcing bash_completion. define $COMP_TAR_INTERNAL_PATHS *before* sourcing bash_completion.