You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have a ~/[hello]/.editorconfig file with a pattern for /*.c, its settings aren't applied because the code ends up matching ~/[hello]/myfile.c against the pattern ~/[hello]/*.c. We could fix the problem by quoting the special chars like [ but it's kind of silly to do that (and it's more work for fnmatchp and won't hit as often in its cache) when we can instead match myfile.c against *.c.
I pushed a patch which does the latter to the scratch/editorconfig (in nongnu.git).
To consult that branch you can do:
The new code passes all the tests for me. The branch includes a few other changes I think we should include, but do let me know if there's some objection to any of those changes, of course.
The text was updated successfully, but these errors were encountered:
If I have a
~/[hello]/.editorconfig
file with a pattern for/*.c
, its settings aren't applied because the code ends up matching~/[hello]/myfile.c
against the pattern~/[hello]/*.c
. We could fix the problem by quoting the special chars like[
but it's kind of silly to do that (and it's more work forfnmatchp
and won't hit as often in its cache) when we can instead matchmyfile.c
against*.c
.I pushed a patch which does the latter to the
scratch/editorconfig
(innongnu.git
).To consult that branch you can do:
The new code passes all the tests for me. The branch includes a few other changes I think we should include, but do let me know if there's some objection to any of those changes, of course.
The text was updated successfully, but these errors were encountered: