Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Underlining broken in 0.200 #544

Closed
keirlawson opened this issue May 22, 2015 · 9 comments
Closed

Underlining broken in 0.200 #544

keirlawson opened this issue May 22, 2015 · 9 comments

Comments

@keirlawson
Copy link

Has been for a few versions, finding this with both ESLint and JSHint linters. Other forms of notification all work. Am using Fedora Linux.

@iam4x
Copy link
Contributor

iam4x commented May 25, 2015

Can't reproduce it, do you have linter-jshint and linter-eslint working together?

@keirlawson
Copy link
Author

Yes, though each is set to disable when the relevant rc file is not present in the project root. This issue persists even when I disable one of them though. Any suggestions on how to debug further?

@floatdrop
Copy link

I have atom 0.201.0 and linter does not have gutters or underlining - but linter are working (in status bar errors are shown).

Any details I can provide for you?

Linter 0.12.6, linter-jshint 0.1.5

@keirlawson
Copy link
Author

Seems to be working for me again in 0.204, linter 0.12.6, linter-jshint 0.1.6. linter-eslint 0.5.8

@jacinto123
Copy link

I have the same issue, gutters and underlining arent working, 0.206, linter 0.12.6, linter-jshint 0.1.6

@varemenos
Copy link

Same problem here, linter works in status bar but not the highlighting

@ghost
Copy link

ghost commented Jun 11, 2015

any ideas on why it isn't working? when i installed 200 it stopped working, i thought it propably will fix itself a few versions later, but now that were on 207 and it still isn't fixed its getting kind of annoying having to work without linter indicatiors.

is there any way i can provide information to help fixing the issue?

@jacinto123
Copy link

Yeah I am still having this issue, is there anything I can provide to help debug this?

@jmurphyau
Copy link

I ran into this issue and worked out how to replicate it.. Install two linter for one file type (e.g. linter-jshint and linter-jscs then disable one..

The config for the disabled one remains in you config.son resulting in the disabled linter still in @linters (coming from @allLinters) - but the linter never runs and the following never gets executed

processMessage: (messages, tempFileInfo, linter) =>
...
if tempFileInfo.completedLinters == @linters.length
....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants