Wrong usage string for trailing varargs

[matklad]

For the following code

        .args_from_usage(
            "[daemon] -d   'Daemonizes the container'
             --cpu [PREC]  'set CPU usage limit'
             <IMAGE_PATH>  'path to image of container file system'
             <CMD>         'command to run inside the container'
             [ARGS]...     'arguments to pass to the CMD'")

I get this usage string: aucont_start [FLAGS] [OPTIONS] [ARGS] <IMAGE_PATH> <CMD>.
[ARGS] should definitely come after IMAGE_PATH and CMD in the usage string. The parsing itself works correctly.

[kbknapp]

Thanks for taking the time to file this! I can confirm, on 1.4.3 this is the case. I believe this may be a bug in the usage generation portion because in cases like the above it should be:

USAGE:
    aucont_start [FLAGS] [OPTIONS] <IMAGE_PATH> <CMD> [--] [ARGS]

Note, you can also override the usage string to make it anything you like, but doing so manes you no longer get context aware usage strings generated on error messages. This doesn't appear to be a good case for that, but just FYI.

We'll report back here once this bug is fixed 👍

[kbknapp]

Also, this is somewhat muddled by the use of ARGS for the argument name, and claps use of [ARGS] in regular usage strings just to denote "optional positional arguments." It's not a big deal, but just something to be aware of.

[matklad]

Thanks for the swift reply! I'd like to add that implementing #278 would be ideal for my use case :)

[kbknapp]

That's actually what I'm working on now, and should be implemented shortly :)