Remove scripts directory in favor of using the functions/ or root
for sharing scripts. Using a scripts directory does not solve the
main problem of sharing scripts with the same name, so this addition
was deemed of little value. In the future, a more robust way to avoid
name collisions when sharing scripts would be nice to have, but at
the moment having a scripts directory is not solving this problem
but just adding clutter to the configuration.
Closes#105.
Obviously this should be the other way around, otherwise, the
user would not be able to modify any variables that have an
effect when Fisherman starts.
In other words, when users install Fisherman, the code in
config.fish should be added before sourcing Fisherman
configuration and not after (current way).
+ Now __fisher_plugin_uninstall_handler is aware of a third argument,
`option` that can be used to indicate the event handler or uninstall
file abot any options available in `fisher uninstall`, namely, --force.
+ In addition, the uninstaller mechanism no longer receives the name of
the plugin, as this information is usually already available to plugins
anyway.
+ Finally, a path to the parent directory where the uninstall.fish file
is located is given instead of the full path to the file. Again, the
plugin usually knows the name of the file, `uninstall.fish`.
Split help command functionality into individual functions
for cosistent with the way other commands are structured,
and improve tab completion times by skipping the overhead
of calling fisher_help directly.
* Add Mizuki to THANKS for help with Japanese translation of the QuickStart Guide.
* fisher --list should return 1 (fail) if no plugins are installed. Closes#101.
* More consistent style 'Usage' instead of 'usage'.
* Silence index check in case $fisher_cache/.index does not exist.
* Add more descriptive message if plugin is not found.
* Silence search failure in case $fisher_cache/.index does not exist.
* Move AUTHORS -> THANKS and remove automatic generation.
THANKS is more sensible than AUTHORS. CREDITS was second best.
Also, after perusing similar files in other projects I noticed
some entries lacking a valid email address and decided fow now
this file should be curated manually to make sure each entry
contains a useful link. This allows users who have contributed
to the project ways other than committing code to be added to
the list as well.
* Rename wait -> spin.
* Remove extra padding in links. (Cosmetic)
* Update to reflect API refactorings.
* Fix bug causing brackets to show up in description.
* Implement using spin function.
* __fisher_gist_to_name uses curl to query the GitHub API which will
return a JSON stream even if the Gist could not be found. So, it's
not possible to determine whether we failed or not using our spin
function and actually need to check the returned string to see if
it contains a valid name or not.
* Let git pull write errors to stderr.
* Use new internal __fisher_spin.
* Extract spin to independent / external module and tweak Makefile
to better integrate with new install process.
+ 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.
