delimited, awk-friendy format and put it in .cache/.index.
During the process, sort the data also. This way, don't need
to repeat the same process every time we run ls-remote.
Add completions for ls-remote with plugin name and info.
when updating the index for ls-remote.
Allow ls-remote to accept a key and always print record if it
matches the plugin's name. Works with the format string too.
Close#234, #236, #238
Running fisher ls-remote will query the GitHub API for all the
repos in the fisherman org and retrieve the JSON file which is
saved to .cache/fisherman/.index.json.
This file is updated every half and hour whenever you run the
command again. This number is subject to change in the future
as we learn how people are actually using this option.
The ls-remote option can take --format=<fmt string> option used
to customize the list output.
By default, it shows only names and breaks it into columns as
wide as your terminal window.
<fmt string> can contain \t tabs or \n line breaks and one or
more of the following variables with information about plugins.
* %name
* %info
* %url
* %stars
ln -F is relevant only when the target is a directory, in which
case `ln` will delete the directory so that the link can occur.
In fisherman, we use links in only two places:
1. Linking files into .config/fish/{functions,completions}, and
2. Linking local plugins into the .config/fisherman
If my calculations are correct, we don't need -F in either case.
Both {functions/completions} never contain directories, so (1)
is probably safe. The fisherman config only contains directories
to installed plugins, so not using -F actually prevents the user
from overwriting a plugin currently installed with a local plugin.
The previous implementation was creating a nested copy of
the target directory (updated plugin) inside the cached
copy.
After some research, I believe there are two things we
can do here:
1. Remove the target and create a new copy or
2. Use the following syntax
cp -rf src_dir/. target_dir
which seems to do what we want, overwrite target with
source entirely.
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!
