[spell check] markdown parsing ignores last character before closing bracket #585
Comments
|
Confirmed, why this happens only with markdown... |
titoBouzout
added
C: Spellcheck
C: Default Packages
T: bug
S: minor
S: trivial
and removed
S: minor
labels
|
Also noticed this a long why ago but didn't really bother to create an issue. Pretty annoying in the occasions when I'd actually want to use spellcheck. |
|
Note that this also affects backticks (i.e., `) when used to denote inline code blocks, as in: In this case, "some" will be marked as misspelled because it only sees "som". |
|
Reopening due to regression introduced in build 3090. Further info in this forum post. |
|
may regression tag could be a good idea /cc @FichteFoll @qgates |
|
Sounds like a good idea to me; this seems to be happening more often lately. I would suggest opening a new issue for previously-fixed issues however (not issues that haven't been fixed properly, like #239). I would also classify "regression" as a type probably, which is a sub-type of "bug". All regressions are bugs, since they used to work differently. Okay? |
|
Concur; it's a no-brainer. Apart from anything else, it's particularly useful for Jon to prioritise fixes to builds that broke previously working functionality. |
|
The regression is now tracked in #937, since this issue has been taken care of. |
Windows 7 Professional 64-bit
ST3: 3065
Language: Markdown
Spell check incorrectly assumes the last character of a word preceding a closing bracket
]is not part of a word.In the context menu, Spell check correctly suggests "something" as the proper spelling and injects this correction in-place:
Seems as though the spell check parser for Markdown misfires on punctuation delimiters.
The text was updated successfully, but these errors were encountered: