Eliminating false positives with the spell-checker

Here are some concrete examples on what I consider false postives with the spell-checker.  If I should submit a feature request in YouTrack, please let me know.

"""
The below example is indeed a spelling error since the

word typo is misspelled as tyypo
"""

# example 1 / should be an error, all lower-case
# tyypo

"""
In the below comments, all below examples (in my opinion)
should be considered false positives for spell-check errors
and not have been flagged.
"""

# example 2 / should not be spelling error as all upper-case
# TYYPO

# example 3 / should not spelling errors since includes numeric characters
# tyypo1234
# TYYPO1234
# t1y2p3o0

# example 4 / should not be spelling error since errant word is part of a larger "word" with embedded punctuation
# typpo:errors
# tyypo&errors

# example 5 / should not be spelling error since the errant word is contained within single quotes
# 'typpo'

# example 6 / should not be spelling error since the errant word is contained within double quotes
# "tyypo"

Cheers,

Rob

Hello Rob,

At the moment the spellchecking plugin doesn't provide any fine-grained configuration

possibilities. You're welcome to file YouTrack issues for specific cases

which are incorrectly reported as typos.

Love the spell-checker but am wondering if there are any tricks /

rules for reducing the number of false postives?  Examples of false

positives would be things like capitalized words, words with numeric

characters, words within single or double-quotes, etc.

So far the only preference options I've been able to uncover are

larger picture types of things like pointing to a customer dictionary

(project settings -> spelling) or only apply the spell-checker to code

and/or literals and/or comments (ide settings -> inspections ->

spelling -> typo).

Cheers,

Rob

---

Original message URL:

http://devnet.jetbrains.net/message/5281665#5281665

--

Dmitry Jemerov

Development Lead

JetBrains, Inc.

http://www.jetbrains.com/

"Develop with Pleasure!"

At the moment the spellchecking plugin doesn't provide any fine-grained configuration

possibilities. You're welcome to file YouTrack issues for specific cases

which are incorrectly reported as typos.

--

Dmitry Jemerov

Development Lead

JetBrains, Inc.

Hi Dmitry,

Thanks for the reply.  I wrote up the enhancement in YouTrack.  Here is a link to the new feature request:

http://youtrack.jetbrains.net/issue/PY-2613

Cheers,

Rob

The eager-beaver spell checker is at it again. Latest PyCharm 2020.2.1 flags commented-out code with prefixed, single-quoted strings, as if they were apostrophes, for example:

# rate_request.SpecialServiceTypes = b'DANGEROUS_GOODS'

We would not want to b'dangerous, would we.

With every new release it's like the warnings have been fed more caffeine...

Indeed, looks like bug, we'd appreciate if you report it to https://youtrack.jetbrains.com/issues?q=%23idea%20%23%7BEditor.%20Spellcheck%7D%20