Nate Cook

@fboundp Thanks for the report and your research into this! I think the best resolution here is to add the workaround as a suggestion in the error message.

#547 should improve the error message when this happens, so that at least it's describing the problem accurately. @timwredwards Can you provide some more detail on your project and what...

> Ideally, it would be great to produce a meaningful warning/error when a valid run() is not found. It obviously fell through to a point where “USAGE” text was displayed....

This might just be a documentation issue — IIRC `.file` will also autocomplete directories, since the file you want might live in a directory. Since files can't contain anything else,...

Great spot, @MaxDesiatov — it would be great if these could preserve their titles when nested. What do you think the behavior should be if the "parent" option group also...

@bartekpacia Thanks for this report! I've heard of this issue from some others who have oh-my-zsh installed, but I haven't been able to reproduce this myself, even after installing that...

As currently configured, SwiftPM is the supported tool for building and running tests on the Mac. If there's a way to expand CMake support, that would be great to see!

Given the headaches and challenges around supporting the sync and async versions of `run()`, I'm reticent to provide another overload here. As a workaround, you can perform any async validation...

Maybe instead of marking these `QUIET`, we could add an additional message that contextualizes the output?

Sorry you ran into this, @MaxDesiatov! There's a default implementation of the `run()` method for all parsable commands, since for intermediate commands in a command hierarchy, there's generally nothing to...