-
Notifications
You must be signed in to change notification settings - Fork 23
Linter not showing errors on OS X #172
Comments
What version of |
The constant spinning circle means that the worker thread got hung up somewhere. I have a fix for this checked in, will be in v1.5.0 (about to release now). After that, the console should also tell you the error that TSLint itself is hitting |
Please try now with v1.5.0 =] |
@Xapphire13 @Arcanemagus With 1.5.0 the error was caught, apparently tslint was thinking the file I was editing was a directory and was causing an ENOTDIR error. I updated to tslint 5.3.2, which gets rid of that error when I use the local tslint. However, the linting still only happens when I save. Typescript errors from the atom typescript package show immediately as I type them, but tslint errors aren't shown until a few seconds after I save. Is this normal? I'm pretty sure on my linux machine they show on change rather than save. |
Hmm that's odd. On my machine linting errors appear real-time. I don't have access to a Mac to test on unfortunately either. Are both your Mac and Linux boxes using the same version of |
I have this exact issue:
Edit: As mentioned here, The fix for me was to quote the glob string. Hopefully that works for you. |
Debug output:
On my Arch Linux machine with identical
.atom
directory, it is working fine. On this mac, I just see a constant spinning circle, and when I hover over that I see:But no tslint errors are shown in any way. Oddly, if the "Fix errors on save" option is enabled, certain errors like whitespace issues are fixed on save but never shown in the editor.
If I disable the "Try using the local tslint package" option, the linter shows errors but only on save.
The text was updated successfully, but these errors were encountered: