From 90b274ef8e11e78262372333a5eea6da5f2df7f7 Mon Sep 17 00:00:00 2001 From: Hong Xu Date: Sun, 15 Sep 2024 18:28:50 -0700 Subject: [PATCH] Clarify the effects of path separator (#49) * Clarify the effects of path separator This is consistent with the rules from `.gitignore`: > If there is a separator at the beginning or middle (or both) of the > pattern, then the pattern is relative to the directory level of the > particular .gitignore file itself. Otherwise the pattern may also match > at any level below the .gitignore level. Since we intend to be consistent with `.gitignore`, this part of the spec has been unclear. Fix editorconfig/editorconfig#509 * Update index.rst Co-authored-by: Chris White --------- Co-authored-by: Chris White --- index.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/index.rst b/index.rst index 74f1120..749bdab 100644 --- a/index.rst +++ b/index.rst @@ -160,6 +160,13 @@ special characters for wildcard matching: - any integer numbers between ``num1`` and ``num2``, where ``num1`` and ``num2`` can be either positive or negative +If the glob contains a path separator (a ``/`` not inside square brackets), then the glob is relative +to the directory level of the particular `.editorconfig` file itself. +Otherwise the pattern may also match at any level below the `.editorconfig` +level. For example, ``*.c`` matches any file that ends with ``.c`` in the +directory of ``.editorconfig``, but ``subdir/*.c`` only matches files that end +with ``.c`` in the ``subdir`` directory in the directory of ``.editorconfig``. + The backslash character (``\\``) can be used to escape a character so it is not interpreted as a special character.