On 10 Jun 2020, Sławomir Stańczak wrote:
>
>$ tar -cf 000/<TAB> not working
If I understand correctly, you would like for 'tar -cf <TAB>' to
complete with tar files already present in the file system. Although I
believe that this would be a reasonable thing to do, upstream
bash-completion seems to believe that there's no point in doing so, as
can be seem in the current code [1]:
# Generate completions for -f/--file.
__tar_file_option()
{
local ext="$1"
case "$tar_mode" in
c)
# no need to advise user to re-write existing tarball
_filedir -d
;;
*)
_filedir "$ext"
;;
esac
}
On the other hand, Ville Skyttä, the current upstream maintainer,
suggested, in the past [2], that the behavior you expect could be a
good thing.
I'll try to come up with an upstream patch.
Cheers,
Gabriel
PS: This bug is similar to https://bugs.debian.org/619548, which I
closed on the assumption that upstream wouldn't want this change. Now I
believe I shouldn't have closed it at all, so I'll use this new bug to
track this. Thanks for the report.
[1]
https://github.com/scop/bash-completion/blob/master/completions/tar#L215-L229
[2] https://bugs.debian.org/618734#68
