A lot has changed, in fact, fisherman as you knew it, is
no longer with us. Let me explain. The new fisherman, is
in fact a rewired clone of ``fin´´, a short-lived 2 week
experiment that started because it was easier to rewrite
everything than moving fisherman forward.
Let me explain. I was longing for a lightweight, simpler
fisherman with minimal maintanance cost. This fin lad is
one of the most pragmatic pieces of code I've ever written,
but attempting to maintain two drastically different plugin
managers was not a sane decision. fin's goal was to get out
of my way and let me be productive with fish and it did.
Now fin is fisherman and fisherman is fin. The most notable
change is that fisherman no longer depends on an index, so
like fin, it's neutral and agnostic to what plugins you use.
No index means fisherman completions are no longer as clever
as to show you description of plugins, but you will still get
enough information to know whether the plugin is a theme or not.
I hope you always check the plugin's README / online docs before
installing anything anyway.
With the index gone, we had no use for ``search``, so this command
is also gone.
If you were using search often or depended on the removed features
above, I am afraid they are gone *gone*, but trust me it's all for
the very best.
Now, with this out of the way, it's all unicorns and dartfish. Almost.
To upgrade to fisherman 2.0.0 you need to REMOVE your current version
of fisherman:
1. ```rm -rf "$fisher_home" "$fisher_config"```
2. Open your config.fish and remove the fisherman initialization code.
3. ```exec fish < /dev/tty``` to reload the session.
4. Run `curl -Lo ~/.config/fish/functions/fisher.fish --create-dirs git.io/fisherman`
That's it. Probably.
The new fisherman brings a lot more stability and maturity to the
project and we need this change in order to move forward. I will
be actively fixing any bugs that may have sneaked in during the
```fin->fisherman``` rewiring, but please do ping me:
@bucaran on GitHub or directly to my email j@bucaran.me
if you find anything out of place. Feel free and invited to go
wild with issues in order to get this into shape ASAP.
Cheers!
Notable changes:
+ Now fisher list does not show plugins that are disabled,
but available in the cache. To preview these items use
fisher list --disabled.
+ Welcome aboard @orangecms and @xrain0610.
+ Fisherman is now available in AUR, thanks @orangecms.
+ Fix load order during installation. Now snippets can
safely invoke functions defined in the plugin function
directory. Thanks @orangecms. #170.
+ Fisherman **installs and updates plugins ⌁concurrently**.
Performance may vary, but if you can see 5 to 10 times
faster network times, it's working well.
of the next line has problems, at least on my machine running cygwin.
It produced an error like this:
~/.local/share/fisherman/functions/__fisher_plugin_validate.fish (line
42): | sed -E "
^ from sourcing file
~/.local/share/fisherman/functions/__fisher_plugin_validate.fish
called on standard input
This change simply eliminates the \ line continuation and instead
concatenates with the next line. It seems simple enough and avoids
this problem, making it work on cygwin.
Handle the case when the user tries to install a plugin that is
a function, but a directory of the same name already exists in
the current working directory.
* Fix bug in fisher_config_color_reset not declaring path variable.
* Silence Git checkout standard error to prevent update failures in some edge cases.
* Revise and correct errors in the documentation and README.
* Add more instrumentation to fisher_plugin_disable.
* Minor doc updates.
