(question) catching linter errors

[mschuchard]

When using atom-linter to execute a linter (e.g. eslint, rubocop, flake8) on the file currently being edited, as in the way most of the linters are doing (return helpers.exec(atom.config.get('linterExecutablePath'), args, {stream: 'stdout'}).then(output => {), is there any way to catch errors thrown by the linter?

I skimmed index.js and nothing jumped out at me.

[steelbrain]

.catch(function(error) { console.log(error); throw error })
It returns a promise, it's easy to chain promises
Check out Promise on mdn

[steelbrain]

Also linterExecutablePath is an invalid config key, it should be package-name.linterExecutablePath

[mschuchard]

Thanks for the tip. I basically need this so that python IOError is ignored. It does not seem that Javascript is robust enough to handle something that granular, but I will try to figure out if and how to get this working.

Also linterExecutablePath is an invalid config key, it should be package-name.linterExecutablePath

Yeah I was trying to write general 'foo' code and apparently failed.