@phlptp thoughts? This was changed in 2.6.2. We could introduce a new mode for the strict stop at any option mode. Or we could reintroduce the old mode, though that's more churn since this has only been out in one patch release. (This PR is just the revert, but any path is possible)

the prefix_command mode has caused a bit of confusion over time. I remember several issues raised of it not working as expected and the previous behavior being confusing to people. So the previous behavior caused some issues and confusion, especially when used in combination with fallthrough and allow_extras. The current behavior made that clear to better match the documentation, but I guess there were those depending on the nuances of the behavior. I think the intended case is putting prefix_command on a subcommand with no option so that command dumps everything remaining since there are no valid options after that, or with a new mode using -- the complexity comes when adding prefix_command on an app/subcommand with existing options or fallthrough or allow_extras that it can interact with the parent options and get some odd behavior. I think my preference would be to leave the current behavior as is, as I would argue that it is clearer than before, and to address this issue add a PositionalOnly mode that turns off the while loop for unknown arguments.

Ahh, I wish it wouldn't auto-push. I'll comment or undraft when happy with it. Edit: looks pretty good, ready for review.

🤖 AI text below 🤖

Reworked as suggested: the revert is dropped, PrefixCommandMode::On keeps the current (2.6.2) behavior, and a new PrefixCommandMode::PositionalOnly provides the stop-only-at-positionals/-- behavior as an opt-in mode. Title and description updated.