"Dr. Adam Nielsen" <admin@xxxxxxxxxx> writes:
> + - A pattern that contains a non-trailing slash is matched
> + For example, `doc/frotz/` matches `doc/frotz` directory, but not
> + `a/doc/frotz` (relative from the `.gitignore` file).
> + Note that the pattern `doc/frotz` and `/doc/frotz` have the
> + same effect in any `.gitignore` file, while `/bar` and `bar`
> + have not the same effect (`/bar` will not match `foo/bar`).
The "note" is not incorrect per-se. The behaviour described is
because the leading slash is removed for the purpose of textual
matching against paths, but still counts as a non-trailing slash for
the purpose of anchoring the pattern to the level of recursion.
I am not sure if that is obvious to the readers, though. Especially
because the "a leading slash matches the beginning of ..." which was
in the original is still left and appears two bullet points after
this one, the presentation order seem a bit suboptimal.
How about deleting that "A leading slash matches the beginning..."
bullet, and then splitting the above bullet into two? That is
- A pattern that contains a non-trailing slash is matched
For example, `doc/frotz/` matches `doc/frotz` directory, but not
`a/doc/frotz` (relative from the `.gitignore` file).
- A leading slash, if any, is implicitly removed before matching the
pattern with the pathname, but the pattern still counts as having
a non-trailing slash for the purpose of the above rule. For
example, a pattern `{asterisk}.c` does not have any slash in it,
so it would match a file or a directory whose name ends with `.c`
anywhere in the directory that has `.gitignore` file in it
(e.g. `sub/foo.c`, `bar.c`). By prefixing a slash to make it
`/{asterisk}.c`, it can be limited to match only at the current
level (i.e. `bar.c` but not `sub/foo.c`).
> + - An asterisk "`*`" matches anything except a slash.
> + A pattern "foo/*", for example, matches "foo/test.json"
> + (a regular file), "foo/bar" (a diretory), but it does not match
> + "foo/bar/hello.c" (a regular file), as the asterisk in the
> + patter does not match "bar/hello.c" which has a slash in it.
s/patter/&n/
> + The character "`?`" matches any one character except "`/`".
> + The range notation, e.g. `[a-zA-Z]`, can be used to match
> + one of the characters in a range. See fnmatch(3) and the
> + FNM_PATHNAME flag for a more detailed description.
>
> - A leading slash matches the beginning of the pathname.
> For example, "/{asterisk}.c" matches "cat-file.c" but not
Then this last paragraph can be removed.
