+ Add the ability to install plugins from Gists. You can
distribute a very simple, one-single function plugin in the
form of a Gist. Your users can install it using fisher
install url and Fisherman will query the Gist using the
GitHub API to get a list of the Gist files and use the name
of the first identified *.fish file to name the plugin in
your system. Since there is no formal way to name a Gist,
and you may prefer to keep the "description" field for the
actual description and not a name, Fisherman supports only
one fish file per Gist. Closes#75.
+ Use command(1) when calling non-builtins. Thanks @daenney.
Closes#79.
+ Add __fisher_plugin_can_enable to detect installing a
prompt that is not the current one. Closes#78.
+ Remove the ability to install a plugin in a parent
directory using .. or ../ or even worse, ../../ as well as
other combinations that navigate to a parent directory. I
find the use case odd at best, and more dangerous that
useful. If you want to install a local plugin use the
full path or a relative path, always top down. fisher
install . or fisher install my/plugin or fisher install
/Users/$USER/path/to/plugin. Closes#81.
By using `command` we ensure that we always end up calling the external
binary and don't get caught by user aliasses, functions or other
magic.
Closes#79
Due to how the completions/*.fish path was traversed
inside __fisher_plugin_walk, the plugin enable/disable
mechanism would fail to copy all completions other than
completions/<plugin>.fish into the config.
Before this commit, both error and success information
was sent to stderr. Now, the total number of plugins
installed / updated / uninstalled is sent to stdout
allowing us to parse this output and implement a
more robust (and simpler) __fisher_deps_install
