mirror of
https://github.com/jorgebucaran/fisher
synced 2024-07-02 23:11:48 +02:00
5dc1eea953
+ 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.
13 lines
397 B
Fish
13 lines
397 B
Fish
function __fisher_plugin_can_enable -a name path
|
|
|
|
# Check whether a plugin is the current prompt or not a prompt. We use this
|
|
# method when the user is trying to Update or Uninstall a prompt that is not
|
|
# currently enabled, and we wish to skip only the enable / disable phase.
|
|
|
|
if not __fisher_path_is_prompt $path
|
|
return 0
|
|
end
|
|
|
|
test "$name" = "$fisher_prompt"
|
|
end
|