GitLab

Attention @maybebtc @mappum

I cleaned up + simplified the main flow. Now, all printing
is contained inside main itself! (:cheer:). I do this with
the help of a cmdInvocation struct that has both
a Parse and Run. The only major clunkiness left is that the
"CallCommand" is still its own function. But *shrug*.

Please test it works as we would expect. i changed much of
the flow, so likely that i missed a complicated edge case.

main roadmap:
- parse the commandline to get a cmdInvocation
- if user requests, help, print it and exit.
- run the command invocation
- output the response
- if anything fails, print error, maybe with help

@mappum

License: MIT
Signed-off-by: Brian Tiger Chow <brian@perfmode.com>

@mappum any idea what might cause the type to not match here?

@whyrusleeping @jbenet

is this non-deterministic?

fix(mount_unix) rm extraneous error

@mappum this one is straightforward, but tagging you here just in case

@mappum can you just sanity check me here with a quick LGTM CR?

@mappum, could you provide a quick LGTM?

@mappum, could you CR this and let me know if I've interpreted the
desired behavior correctly?

NB: return variables are provided for clarity. Otherwise, it's not
entirely clear that the bool is for _found_.

TODO add tests for remaning, untested methods.