Repository navigation
Request for way to disable "xspec" extension-based completion #1067
Description
Activity
It should be reasonable that emptying
_comp_xspecsdisables all the xspec completions.# Note: Currently this doesn't work declare -gA _comp_xspecs=()
However, it doesn't work currently because emptying
_comp_xspecsleaving the completion settings-F _filedir_xspecdisables any filenames.- added a commit that references this issue
on Nov 18, 2023 @duelafn I realized that the above setting actually works with the current implementation (except for
7z,file-roller, andjar, for which_filedir_xspecare directly called internally). When the_comp_xspecsentry does not exist, the completion loader does not set up_filedir_xspecin the first place. If you are using the release version, you need to empty_xspecsinstead of_comp_xspecs. In summary, you can add the following setting immediately after loadingbash_completion:declare -gA _comp_xspecs=() _xspecs=()Thanks for the update - I was just experimenting and came to the same conclusion (that clearing the array works currently and that clearing _xspecs works for the ancient release included in Debian). Fantastic!
Hello, I often work with files with missing or incorrect file extensions and the builtin extension-based completions for things like unzip make this difficult. I am aware that I can undo individual completions by ading, say,
complete -o default -o bashdefault unzipto my .bashrc (and I'm currently doing this for the most common offenders), but really I'd rather be able to fully disable extension-based filtering for all commands without having to continually update my list of exceptions.I'm hoping for some kind of environment variable that that I can set even after loading bash-completion that will make, at least, the "_filedir_xspec" function fall back to normal file matching (maybe something like
BASH_COMPLETION_DISABLE_EXTENSION_FILTERS).Thanks for some great software and thanks for considering my feature request!