AtomLinter / linter-spell

Multilingual grammar-specific spell checking for Atom and linter using Ispell compatible interface such as GNU Aspell or Hunspell.
https://atom.io/packages/linter-spell
MIT License
14 stars 1 forks source link

Selecting spelling suggestions occasionally causes improper corrections #63

Open mlangiu opened 6 years ago

mlangiu commented 6 years ago

The correction process of linter-spell doesn't seem to be working properly for me. I typed the sentence

" It would be so naice if tihs woudl be correctted!"

into a text file, here's what happened:

When all words are "corrected", I end up with something like (there are different outcomes, see the screenshot):

" It would be so nice if tthiswwouldbe ccorrected"

Note how it seems like the position where a corrected word is entered is sometimes offset by one character.

xavoh commented 6 years ago

I also experiencing this problem, but the posistion of the corrected word is sometimes offset by several lines/characters. This happens frequently and makes linter-spell unusable for me right now.

An example is shown in the two screenshots below:

screen shot 2018-04-23 at 19 41 39

screen shot 2018-04-23 at 19 41 50

Note how the correction LHCb -> LHC has taken place two lines above causing special -> sLHCal.

I see this issue with plain text documents as well as latex documents. I have not experimented with other document types.

List of current packages: atom-material-syntax@1.0.8 busy-signal@1.4.3 colorblind-wombat-dark-syntax@0.6.0 intentions@1.1.5 language-latex@1.1.1 latex@0.50.0 linter@2.2.0 linter-spell@0.15.0 linter-spell-latex@0.11.0 linter-ui-default@1.7.1 multi-cursor@2.1.5

Atom version: 1.26.0 x64 OS: Mac OS X El Capitan 10.11.6

This problem only appeared after I did an update of all my packages today, during which the following packages updated: atom-material-syntax latex linter-spell-latex linter-ui-default multi-cursor However, I didn't take note of what packages versions I was using previously using. I had not updated any packages since 8th October 2017, if that helps.

Reverting linter-ui-default to linter-ui-default@1.6.10 (apm install linter-ui-default@1.6.10) seems to fix the issue.

For reference I also see issue #46 like the poster above.

DavidDreher commented 5 years ago

I have the same issue and it makes it hardly usable. Sometimes just saving before changing a word helps, but this is not a 100% fix, since sometimes it still changes at a random position.

Also reverting the linter-ui-default package to 1.6.10 did not fix the issue for me.