fix(ex_cmds): improve E77 glob expansion message#39843
Conversation
|
(see previous: #39829) Please refrain from using copilot for future PRs; it's noisy. Just run copilot on your own machine. |
0fe10fd to
2651bcf
Compare
Problem: The E77 help text only described glob expansion, even though the error can also be raised by explicit multiple file names. Solution: Describe both explicit multiple names and glob expansion in the E77 help entry. AI-assisted: Codex
|
|
||
| *E77* > | ||
| Too many file names | ||
| Too many file names (glob not allowed) |
There was a problem hiding this comment.
I find the (glob not allowed) misleading here since as explained just below, it doesn't necessarily implies a glob was used
There was a problem hiding this comment.
Adjusted this in 36e03ab: E77 now says "Too many file names (only one allowed)", and the doc text below keeps the glob-specific :next hint.
There was a problem hiding this comment.
we are going in circles. this was already settled in #12139
the minor risk of "misleading" is outweighed by the UX improvement for other cases
|
I checked the current failed Windows functional run. The changed I tried to rerun the failed job, but GitHub rejected the rerun with |
Summary
:next.:editwith a glob argument.Closes #12139
Test
git diff --check