'fisher update' hangs.

[RafaelCosman]

On C9 Ubuntu machine.

[ghost]

Yes, this could be a problem in machines other than OS X and ubuntu/trusty64, the only two platforms I have tested this until now. The problem appears to be I am using find(1) in a non POSIX way...

The milestone I am working towards will fix this by removing the use of find(1) and adding a simple --cache to fisher to retrieve the relevant stuff from the cache. It's just a loop over $fisher_cache/* letting in paths that validate to test -d.

#11

[RafaelCosman]

Thanks for working on this, @jorgebucaran.

[simnalamburt]

👍

[ghost]

@RafaelCosman @simnalamburt

Guys, I was mistaken and replied to this message shortly after another user had reported a similar issue and claimed it had to do with find(1). This in fact, has nothing to do with that, (probably), and it's just the default behavior of update.

Fisherman has strong ties to the UNIX philosophy, at least it says so in the manual 😄 and one of the things that are common across commands is that streams are prioritized.

So, fisher update will hang because is waiting for input. This allows cool things like:

fisher --cache | fisher udpate

or

fisher update < bundle

[rif]

So what is the recommend way to list/update all installed plugins?

[ghost]

Hey @RafaelCosman

fisher update plugin1 plugin2 ...

fisher update -h
usage: fisher update [<name or url> ...] [--me] [--quiet] [--help]

       -m --me  Update Fisherman
    -q --quiet  Enable quiet mode
     -h --help  Show usage help

If you want to update all the plugins you could try:

fisher --cache | fisher update

[simnalamburt]

I think making fisher update to update all plugins is the best default. Most package managers like npm, gem, etc update all installed plugin when they executed with ~~ update and I think most users are used to it.

Yes fisher --cache | fisher update fits very well with UNIX philosophy but fisher update is also good default, and I think both can coexist with isatty(3) just like as the python binary does.

How do you think?

[ghost]

@simnalamburt Alright. 👍

Can you create an issue indicating this feature request and I will work on it. After thinking about this in my end, I came to the conclusion you are right.

We can always do this:

fisher --cache | fisher update -

[ghost]

fisher update

To update Fisherman.

fisher update -

To read from STDIN.

fisher update a url local_path ...

To update all that stuff.

[simnalamburt]

Perfect