Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 15 00:34
    github-actions[bot] closed #1554
  • Jan 12 12:04
    RamoFX closed #1568
  • Jan 08 03:35
    aminya edited #1570
  • Jan 08 03:35
    aminya opened #1570
  • Jan 01 00:16
    github-actions[bot] labeled #1554
  • Dec 29 2020 09:23
    lierdakil closed #1569
  • Dec 29 2020 09:23
    lierdakil labeled #1569
  • Dec 27 2020 14:15
    Ppang0405 opened #1569
  • Dec 16 2020 13:08
    RamoFX edited #1568
  • Dec 15 2020 17:57
    RamoFX edited #1568
  • Dec 15 2020 15:42
    RamoFX edited #1568
  • Dec 15 2020 15:41
    RamoFX edited #1568
  • Dec 15 2020 15:29
    RamoFX edited #1568
  • Dec 15 2020 15:29
    RamoFX edited #1568
  • Dec 15 2020 15:26
    RamoFX opened #1568
  • Nov 21 2020 21:35
    delucca closed #1567
  • Nov 21 2020 00:22
    lierdakil labeled #1567
  • Nov 21 2020 00:22
    lierdakil labeled #1567
  • Nov 20 2020 13:54
    lierdakil labeled #1566
  • Nov 20 2020 13:54
    lierdakil labeled #1566
Basarat Ali Syed
@basarat
https://github.com/TypeStrong/atom-typescript/blob/master/CONTRIBUTING.md#publishing
@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
blob
blob
@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
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
:(