When I open an SCSS file and scss-lint is not installed on my machine, a console error pops up: "Uncaught error: spawn ENOTDIR" from child_process.js line 1017. This error reappears on save. The document also tends to behave strangely. For example, it may eventually becomes impossible to indent any line. When atom-lint is toggled off, these issues stops occurring. While there's an easy workaround — install scss-lint — I don't want to actually use scss-lint. Perhaps atom-lint is not actually checking to see if a linter exists before attempting to use it for the open file format?
When I open an SCSS file and scss-lint is not installed on my machine, a console error pops up: "Uncaught error: spawn ENOTDIR" from child_process.js line 1017. This error reappears on save. The document also tends to behave strangely. For example, it may eventually becomes impossible to indent any line. When atom-lint is toggled off, these issues stops occurring. While there's an easy workaround — install scss-lint — I don't want to actually use scss-lint. Perhaps atom-lint is not actually checking to see if a linter exists before attempting to use it for the open file format?