Interference between linter-* and not-ready linters

[jcjaskula]

I was never able to use linter-jshint till I found linter-pep257 interferes with it. linter-pep257 is just so far a template and I installed it to be aware of the future updates. I had to disable it to make linter-jshint displaying something.

I opened AtomLinter/linter-jshint#22 but I realized that other linter-pkg (for example linter-pylint) were silent when linter-{pep257,rst} were enable.

Disabling these empty linter-* is a workaround to me.

[iam4x]

@jcjaskula These linters are not ready yet, we only registered the name for atom.io/packages

[jcjaskula]

It is not mentioned anywhere that they interfere with other linters. I installed them to benefit from the automatic update. I was about to drop the idea of using linter-jshint and linter-pylint because of this interference and I can imagine other people did.

I think the issue deserves at least a note in the readme of main package linter and/or any of these not-ready-yet linters.

[iam4x]

@jcjaskula I'll add it on README.md I didn't tried to install them before.