Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 15 09:28
    pasinduperera synchronize #1514
  • Oct 15 09:20
    pasinduperera synchronize #1514
  • Oct 15 09:11
    pasinduperera opened #1514
  • Oct 02 22:01
    kaiyoma opened #1513
  • Sep 30 20:20
    jfellus edited #1512
  • Sep 30 20:20
    jfellus edited #1512
  • Sep 30 20:19
    jfellus edited #1512
  • Sep 30 20:18
    jfellus edited #1512
  • Sep 30 20:18
    jfellus edited #1512
  • Sep 30 20:17
    jfellus opened #1512
  • Sep 21 09:57
    arcanis opened #1511
  • Sep 20 16:18
    reduxdj edited #1510
  • Sep 20 16:18
    reduxdj opened #1510
  • Sep 20 08:28
    mininek opened #1509
  • Aug 15 17:06
    chaffeqa opened #1508
  • Aug 08 16:07
    lierdakil closed #1507
  • Aug 08 16:07
    lierdakil labeled #1507
  • Aug 08 11:43
    rahamin1 opened #1507
  • Aug 07 12:07
    lierdakil labeled #1505
  • Aug 07 12:07
    lierdakil closed #1505
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
blob
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
Screen Shot 2015-07-03 at 10.58.45 AM.png
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
Cu3PO42
@Cu3PO42
:/
Basarat Ali Syed
@basarat
This is their gitter page btw : https://gitter.im/AtomLinter/Linter
Cu3PO42
@Cu3PO42
The joys of being dependant on someone else fixing errors
Basarat Ali Syed
@basarat
we could put in the effort (its oss) ... just because nearly everybody who uses atom uses linter => they will get a clear issue report soon
and they are actively maintaing it :rose:
Cu3PO42
@Cu3PO42
Maybe I’ll look into it after I get sourcemaps working for the node debugger
Basarat Ali Syed
@basarat
blob
what I'm working on ^ typescript/register support
for node
Cu3PO42
@Cu3PO42
That’s awesome!
kpgarrod
@kpgarrod
@basarat: actually, the typescript error doesn't always get cleared
Basarat Ali Syed
@basarat
@kpgarrod ctrl+s should clear that : https://github.com/TypeStrong/atom-typescript#sync
does it?
If so I know I have a bug to find :) lately I haven't needed that
kpgarrod
@kpgarrod
no, it doesn't
Basarat Ali Syed
@basarat
:(
screenshot?
kpgarrod
@kpgarrod
Screen Shot 2015-07-03 at 11.15.18 AM.png
Cu3PO42
@Cu3PO42
Can you consistently reproduce that?
kpgarrod
@kpgarrod
not sure, but it seems to be happening regularly
Basarat Ali Syed
@basarat
in a not so loud voice (at least its not a bug in linter then) ashamed
Cu3PO42
@Cu3PO42
Welp, I can’t seem to be able to reproduce that
In my code
kpgarrod
@kpgarrod
I just updated to 5.0.9 and the errors have gone for now
Cu3PO42
@Cu3PO42
Awesome!
kpgarrod
@kpgarrod
I'll try to watch out for the exact conditions that cause it if it happens again