Re: [PATCH v2] completion: zsh: support completion after "git -C <path>"
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 21, 2026, 16:42 UTC
- Message-ID
- <xmqq5x13qvb5.fsf@gitster.g>
- In-Reply-To
- <CALnO6CCr+CMhB6Pxo7KHExcJ7PBcEQODEJa_PmfguCr_WYVS+A@mail.gmail.com>
"D. Ben Knoble" <ben.knoble@gmail.com> writes:
Show 11 quoted lines
>> [Footnote] >> >> * Look for case_clause in >> https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html >> and read from there. > > Oh, thanks! The Bash manual doesn't admit that case in my reading, but > it clearly does in implementation. Oddly, I seem to recall several > years ago that both Bash and ShellCheck would complain about empty > case arms (I got in the habit of writing ": continue" as a bit of a > comment). Anyway, TIL.
I am afraid that the description in POSIX itself contributes heavily to this common misconception.
Section 2.9.4.3 (Case Conditional Construct)
https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html#tag_19_09_04_05
gives a simplified syntax
The format for the case construct is as follows:
case word in
[[(] pattern[ | pattern] ... ) compound-list terminator] ...
[[(] pattern[ | pattern] ... ) compound-list]
esacand I think that is where the most people go to learn what is and what is not kosher in the standard. But as you saw, this simplified "format" contradicts what the actual grammar, described in Section 2.10 (Shell Grammar) has (notably, you can have linebreak, which is defined to be zero or more NEWLINEs, instead of compound-list there).
https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html#tag_19_10