Note that we generally ask for Issues to be created so we can get alignment before moving onto issues. This avoids wasted time on both sides and helps provide a central point of discussion as multiple PRs may end up existing for one root cause for various reasons.

Our focus is shifting to our new completion system (#3166). While we can still improve the existing completions, I would prefer it to be done in a way that is aligned with #3166. Currently, #3166 generates all completions in a shell-agnostic way. Each shell only has a thin adapter. This means most likely that the problem exists there too.

So the question is how should we handle this in #3166.

Some options:

• Decide this is the right behavior for Stablize Rust-Native Completion Engine Tracking Issue #3166 and extend it to all shells
• Add some per-shell logic in Stablize Rust-Native Completion Engine Tracking Issue #3166
• Decide this is not the right behavior and don't change any shells in either completion system

Sounds reasonable. I'd still like to fix this for the older completions in the meantime before the new completion engine is released.

Few observations:

1. In fish, zsh and nu, the built-in completers behave the same as in PowerShell – you have to type a - first before you get completions for flags. In general, I would be very surprised if there's any shell that prefers to always suggest both positional parameter values and flags, but I did not check.
2. In fish and zsh, the clap-generated completion scripts already works that way. In bash, the completion script returns all possible completions (both values and flags), same as in PowerShell. So, the current state is inconsistent.

PRs are not a place to be discussing what should be done, see again

Note that we generally ask for Issues to be created so we can get alignment before moving onto issues. This avoids wasted time on both sides and helps provide a central point of discussion as multiple PRs may end up existing for one root cause for various reasons.

PRs are not a place to be discussing what should be done, see again

#6219