@Cu3PO42 I added you as a collaborator ... accept that and then you can push ;)
Cu3PO42
@Cu3PO42
@basarat I’m afraid I didn’t receive an invite
Basarat Ali Syed
@basarat
@Cu3PO42 I just cancelled and invited again ... check email again :rose:
Cu3PO42
@Cu3PO42
@basarat Got one and joined!
Thanks :)
kpgarrod
@kpgarrod
I am noticing (for the last few releases) that some errors are not cleared when I fix them. The only way I can get the errors cleared is to close down Atom (or the project at least) and re-open. Is anybody else getting this?
Basarat Ali Syed
@basarat
I am getting something like this. Note that the atom-ts error panel does clear errors, just the linter errors keep hanging @kpgarrod is that correct?
Cu3PO42
@Cu3PO42
I have sometimes noticed that, too, although deleting the line and pasting it again usually does it for me. Using vim-mode that’s just a quick ddP
kpgarrod
@kpgarrod
@basarat. not sure. I will check. Linter errors are shown in the bottom of the screen, right?
Cu3PO42
@Cu3PO42
The linter error list should be below the TS bar.
Basarat Ali Syed
@basarat
the lower one is linter ... it is out of date even right now
kpgarrod
@kpgarrod
How do I attach a file here?
Basarat Ali Syed
@basarat
@kpgarrod drop it ... or paste it from clipboard
kpgarrod
@kpgarrod
Screen Shot 2015-07-03 at 10.58.45 AM
Basarat Ali Syed
@basarat
@kpgarrod was that a drop?
Cu3PO42
@Cu3PO42
This message was deleted
Dropping from OS X definitely works...
kpgarrod
@kpgarrod
sorry, tried pasting
Basarat Ali Syed
@basarat
@kpgarrod press cmd+s does that fix it?
_
kpgarrod
@kpgarrod
You see, I have fixed the error at line 104
there is no coachId there now
As you say, the error disappears from the ts errors
Basarat Ali Syed
@basarat
"disappears from ts errors" "but sticks in linter errors" right?
kpgarrod
@kpgarrod
no, cmd+s does not fix it
even closing and reopening the file doesn't
@basarat: yes, right
Basarat Ali Syed
@basarat
cool It's an issue with the new linter rewrite. I am hoping other lint clients (like us) will suffer the same fate and someone there will fix it :)
It's not particularly easy to reproduce
I've even tried execing "linter:lint" command and even that doesn't fix it