Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

Spell-check no longer works #369

Open

Description

@BFoor

I've toggled it on/off and nothing works.

Activity

  1. xyxyxoxo commented on Aug 15, 2021

    @xyxyxoxo

    Same here, stopped working recently. Using Atom 1.58.0 and spell-check 0.77.1

  2. xyxyxoxo commented on Aug 15, 2021

    @xyxyxoxo

    Downgraded Atom to 1.57.0, spell checker works again.

  3. sanscontext commented on Aug 18, 2021

    @sanscontext

    Chiming in that this is broken for me on Atom 1.58 with spell-check 0.77.1.

  4. dmoonfire commented on Aug 23, 2021

    @dmoonfire
    Contributor

    Is there a chance any of you had spell-check-project? I just found a bug in that that prevented spell-check from working.

    Also, is it entirely not working, or is it highlighting errors and not letting you correct them?

  5. sanscontext commented on Aug 23, 2021

    @sanscontext

    Negative on the spell-check-project, I don't have that installed. There were none of the red-underlines that indicate spelling mistakes at all. Figured this out when a colleague pointed out a misspelling and I realized there'd been no spell-check for a month at least.

    Also in the most infuriating "voodoo debugging" style resolution, I was messing around flipping the locales thing off on without effect, including restarting Atom between attempts. Then my laptop rebooted for a macOS update, and now BAM it's working. 🤔

  6. dmoonfire commented on Aug 24, 2021

    @dmoonfire
    Contributor

    now BAM it's working. thinking

    Well, that makes it even harder to figure out. :)

    @andrei-a-papou and @BFoor, would you be willing to turn on debugging mode for spell-check, restart Atom in debug mode, then go into the console and type:

    localStorage.debug="spell-check:*"
    

    (Hit return after that.) Then hit F5 (reload).

    This should turn on a lot of debugging statements in the console that hopefully will give me an idea of what is going wrong.

  7. Abello966 commented on Aug 30, 2021

    @Abello966

    Hello, I am having the same issues. Doing what @dmoonfire said got me some strange errors:

    DevTools failed to load SourceMap: Could not load content for file:///usr/lib/atom/node_modules/spelling-manager/lib/index.js.map:
    DevTools failed to load SourceMap: Could not load content for file:///usr/lib/atom/node_modules/spelling-manager/lib/BufferSpellingChecker.js.map:
    DevTools failed to load SourceMap: Could not load content for file:///usr/lib/atom/node_modules/spelling-manager/lib/regex-helper.js.map:
    DevTools failed to load SourceMap: Could not load content for file:///usr/lib/atom/node_modules/spelling-manager/lib/SpellingManager.js.map:
    DevTools failed to load SourceMap: Could not load content for file:///usr/lib/atom/node_modules/spelling-manager/lib/TokenCheckStatus.js.map:
    DevTools failed to load SourceMap: Could not load content for file:///usr/lib/atom/node_modules/spelling-manager/lib/TokenSpellingManager.js.map:

    I'm running an Arch Linux instalation
    spell-check 0.77.1
    Atom Editor v1.58.0

    Recently I realized I had the community version of spell-check, so I promptly uninstalled it. It didn't help with the problem nevertheless

    EDIT: I'm at the same time happy and unhappy to tell that upon rebooting my computer it worked again. Not sure what changed in the meantime

  8. 9994444ggg commented on Aug 30, 2021

    @9994444ggg
  9. paul-grassl commented on Sep 29, 2021

    @paul-grassl

    Any update on this? Is downgrading to Atom v1.57 the only way to make it work again?

  10. dmoonfire commented on Oct 7, 2021

    @dmoonfire
    Contributor

    There was a recent change to take debug out. On the settings, it's called "Enable debug information for spell check". Would you be willing to try checking it, restarting Atom entirely, and then see if you still see the problem?

    If so, this might be something missed reference to debug that was left in. I had #361 which addressed some of the issues with enabling/disabling debug, but I'm not sure if they would solve it or not.

  11. paul-grassl commented on Oct 14, 2021

    @paul-grassl

    I enabled debug information and now it seems to work again!! Thank you @dmoonfire

  12. dmoonfire commented on Oct 19, 2021

    @dmoonfire
    Contributor

    Thank you. I think I know how to fix it, but the work-around is to enable debugging and restart.

  13. senornz commented on Oct 19, 2021

    @senornz

    Not working for me on Windows 10 with either 1.5.7 or 1.5.9. Enabling or disabling debug doesn't work for me either

  14. dmoonfire commented on Oct 19, 2021

    @dmoonfire
    Contributor

    @senornz, after you enabled debug, did you restart Atom? I found that it didn't properly turn on debugging until you did a full quit and come back in.

  15. TristynAlxander commented on Apr 21, 2022

    @TristynAlxander

    I'm not sure if I have the same issue or not (linux-mint, atom 1.58.0). The spell check stops working, but it's quite difficult to identify why. It stops when I modify the default grammar list, but when I fix them it doesn't start working. It will start working if I restart atom, but only if I have the default settings. Except that's not entirely true because if I open atom to a particular project (e.g. atom ./) sometimes the spell check is just stuck not working no matter what I do. Enabling/Disabling the debug with restarts does nothing as far as I can tell.

    Few weeks back I had spell check enabled for latex; however, I can't seem to make it work for anything that's not default now. I only wanted to get spell check for python. For some reason I had thought that was already a feature... and in the middle of writing this after having been frustrated and left atom closed for a while I opened the project it would never work in and I have python spell-check presumably from source.python

    Well, that's what I set out for, but I have no idea why it works or doesn't. Best guess is that even when restarting atom it's not fully shut down in some way and needs more time than I was giving it to get itself sorted. Maybe restarting my whole machine instead of just the program would've helped? Again I don't know, but maybe someone more familiar with the inner workings of the program can comment on my experience and maybe that'll help someone.

  16. 9994444ggg commented on Apr 21, 2022

    @9994444ggg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions