fisher/test/plugin-can-enable.fish
Jorge Bucaran 4cfd037cc0 Ahoy! an early v0.7.0 is here!
+ 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.
2016-02-11 09:40:03 +09:00

25 lines
526 B
Fish

set -l path $DIRNAME/.t-$TESTNAME-(random)
set -l plugins foo bar baz norf
set -l prompts baz norf
function -S setup
mkdir -p $path/{$plugins}
touch $path/{$prompts}/fish_prompt.fish
set -U fisher_prompt $prompts[1]
for plugin in $plugins
__fisher_plugin_can_enable $plugin $path/$plugin
echo $status
end > $path/output
end
function -S teardown
rm -rf $path
end
test "$TESTNAME - Check whether a plugin is the current prompt or not a prompt."
0 0 0 1 = (cat $path/output)
end