Fisherman was always writing its completion file to $fish_config/completions.

This was incorrect behavior if $fish_path was set to a directory other than
$fish_config (its default).

Note that when using $fish_path to manage functions, completions and snippets, 
you opt out fish default locations which are handled for you by the shell and
consequently are responsible for appending your custom $fish_path/functions
and $fish_path/completions directories to $fish_function_path and $fish_complete_path respectively, as well as sourcing snippets (.fish files under $fish_path/conf.d) on shell 
startup.
This commit is contained in:
Joe George 2017-06-30 15:19:48 -04:00 committed by Jorge Bucaran
parent 210fb8c202
commit c3172511e0

View file

@ -117,7 +117,7 @@ function $fisher_cmd_name -d "fish plugin manager"
command mkdir -p {"$fish_path","$fish_config"}/{conf.d,functions,completions} "$fisher_config" "$fisher_cache"
or return 1
set -l completions "$fish_config/completions/$fisher_cmd_name.fish"
set -l completions "$fish_path/completions/$fisher_cmd_name.fish"
if test ! -e "$completions"
echo "$fisher_cmd_name --complete" > "$completions"