Document glob alternatives syntax with {} #1816
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This syntax does not exist in `git`, so it is not documented in `man gitignore`. There is a question of whether it *should* exist, but as long as it does, it should be documented somewhere. See also: BurntSushi#1221 BurntSushi#1368
BurntSushi
approved these changes
May 30, 2021
BurntSushi
added
the
rollup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This syntax does not exist in
git, so it is not documented inman gitignore. There isa question of whether it should exist, but as long as it does, it should be documented
somewhere.
See also:
#1221
#1368
Update 1: I'm especially interested in documenting the lack of empty alternatives, since the reason I
started looking for documentation is that I couldn't figure out whether
-g .git{,/*}shouldwork.
Update 2: I like this syntax, but I'd prefer it if it was only valid in the command line (as opposed to ignore files), FWIW. That is, as long as having a slightly different syntax in the command line doesn't introduce too much complexity.