Currently there is no default set for the scss-lint executable. Ideally, the default is to use scss-lint on the $PATH. This works for other linters, but hasn't been tested AFAIK with scss-lint.
A strong complicating factor is that many folks use managers like rvm and chruby, which do not work by just executing scss-lint by default (see https://github.com/AtomLinter/linter-scss-lint/pull/93). Right now the linter throws an error if no exceutable path has been set, which at least lets the user know they need to set it. If there is a default, error handling needs to be graceful enough to provide a similarly descriptive call-to-action for the user.
From https://github.com/AtomLinter/linter-scss-lint/issues/66#issuecomment-145650197
Currently there is no default set for the scss-lint executable. Ideally, the default is to use scss-lint on the
$PATH. This works for other linters, but hasn't been tested AFAIK with scss-lint.A strong complicating factor is that many folks use managers like
rvmandchruby, which do not work by just executingscss-lintby default (see https://github.com/AtomLinter/linter-scss-lint/pull/93). Right now the linter throws an error if no exceutable path has been set, which at least lets the user know they need to set it. If there is a default, error handling needs to be graceful enough to provide a similarly descriptive call-to-action for the user.