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
I have a .codespellrc where I want to skip a special directory (call it A1_X), except for one file. The manpage says that the skip entries support globs. So I went to a glob validator to double check that my glob pattern should match that file. However, codespell does not seem to understand the syntax and checks all files in the directory.
I used skip = ./somedir,./dir/A1_X/**/@(!(SomeCode.c)),./someotherdir in my config file.
For reference here is the direct link to the validator including the values I used:
The text was updated successfully, but these errors were encountered:
darkmattercoder
changed the title
Glob Matching for skip does not work as expected (excluding one file pattern from skipping)
Glob matching for skip does not work as expected (excluding one file pattern from skipping)
Sep 10, 2024
I have a
.codespellrc
where I want to skip a special directory (call itA1_X
), except for one file. The manpage says that the skip entries support globs. So I went to a glob validator to double check that my glob pattern should match that file. However, codespell does not seem to understand the syntax and checks all files in the directory.I used
skip = ./somedir,./dir/A1_X/**/@(!(SomeCode.c)),./someotherdir
in my config file.For reference here is the direct link to the validator including the values I used:
https://www.digitalocean.com/community/tools/glob?comments=false&glob=.%2Fdir%2FA1_X%2F%2A%2A%2F%40%28%21%28SomeCode.c%29%29&matches=false&options=dot%3Atrue&tests=.%2Fdir%2FA1_X%2F.hiddenfile&tests=.%2Fdir%2FA1_X%2Fsrc%2FSomeCode.c&tests=.%2Fdir%2FA1_X%2Fhampelmann&tests=.%2Fdir%2FA1_X%2Fsrc%2Fsubdir%2Fsubsubdir%2FSomeCode.c&tests=.%2Fdir%2FA1_X%2Fsrc%2Fsubdir%2Fsubsubdir%2F
How can I get codespell to understand my configuration?
Codespell used is from commit 2569d89
The text was updated successfully, but these errors were encountered: