Closed silentTeee closed 1 year ago
My previous example had a typo. I'm not sure why the #|
doesn't show up as zef just uses the default cli argument parsing. I suspect a smaller example could be figured out (that doesn't use zef) to report to Raku, but until then I'll reopen this.
I think I was mistaken -- I cannot reproduce the example given in the original issue. At least regarding the missing "Download specific distributions" that you mention isn't showing up:
$ raku -I. bin/zef fetch
Usage:
bin/zef [--force|--force-fetch] [--timeout|--fetch-timeout[=Int]] [--degree|--fetch-degree[=Int]] [--update[=Any]] fetch [<identities> ...] -- Download specific distributions
$ zef fetch
Usage:
zef [--force|--force-fetch] [--timeout|--fetch-timeout[=Int]] [--degree|--fetch-degree[=Int]] [--update[=Any]] fetch [<identities> ...] -- Download specific distributions
as for fetch <identities>
vs fetch [<identities> ...]
, that would indeed still be a rakudo issue as zef declares that parameter as requiring at least one value via *@identities ($, *@)
.
If you think there is still a zef issue here that I haven't addressed, please feel free to reopen.
Context
Running
zef fetch
without any arguments gets the 'Usage' message, when the Usage message itself seems to indicate that all arguments are optional. If my understanding is correct, thenfetch
is supposed to be specifically for downloading source code, and if that's the case then it makes sense that not providing a module name would fail. But that's not what the Usage message indicates.Expected Behavior
Running
zef fetch
shows the following:Actual Behavior
Steps to Reproduce
run
zef fetch
from any shellYour Environment