-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ignore words become case-insensitive if it is only lowercase. #3638
Comments
#2323 could be related. |
The relevant code was introduced by #3272: codespell/codespell_lib/_codespell.py Lines 699 to 707 in 3f0532c
I seem to recall that the spirit of that change is that lowercase words to ignore are handled in a case-insensitive way ( In any case, you're right: at the very least the documentation should have been updated. |
While #2323 is similar, I don't think it's directly related. |
@DimitriPapadopoulos thanks for checking on this, really appreciate that.
unfortunately no, it does not work for our use case. i think this is inconsistent behavior for user perspective. tomoyafujita@~/DVT/codespell >cat test.md
ros2 should not be detected.
ROS2 should be detected.
tomoyafujita@~/DVT/codespell >cat dictionary.txt
ROS2->ROS 2
tomoyafujita@~/DVT/codespell >codespell -D dictionary.txt,- test.md
test.md:1: ros2 ==> ros 2
test.md:2: ROS2 ==> ROS 2
tomoyafujita@~/DVT/codespell >codespell --ignore-words-list ros2 -D dictionary.txt,- test.md
tomoyafujita@~/DVT/codespell >codespell --ignore-words-list ROS2 -D dictionary.txt,- test.md
test.md:1: ros2 ==> ros 2
|
could you take a look at #3658? since this is the 1st time for me to make PR against codespell-project, i would be missing something. but i did went through code and documentation, and i checked local verification is passing. |
according to https://github.com/codespell-project/codespell?tab=readme-ov-file#ignoring-words,
but the following example tells me that is not implemented when word to ignore is only with lowercase.
i believe this is unexpected behavior, at least it is not consistent with documentation above.
The text was updated successfully, but these errors were encountered: