Failed at checking.

[JeffreyStrahm]

Error: spawn UNKNOWN
    at exports._errnoException (util.js:1026:11)
    at ChildProcess.spawn (internal/child_process.js:313:11)
    at exports.spawn (child_process.js:392:9)
    at C:\Users\Jeffrey Strahm\.atom\packages\linter-cpplint\node_modules\sb-exec\lib\index.js:15:53
    at Object.<anonymous> (C:\Users\Jeffrey Strahm\.atom\packages\linter-cpplint\node_modules\sb-exec\lib\index.js:14:18)
    at next (<anonymous>)
    at step (C:\Users\Jeffrey Strahm\.atom\packages\linter-cpplint\node_modules\sb-exec\lib\index.js:84:191)
    at C:\Users\Jeffrey Strahm\.atom\packages\linter-cpplint\node_modules\sb-exec\lib\index.js:84:368

[Arcanemagus]

Do you have any information on how to reproduce this?

[JeffreyStrahm]

I installed it, and when I saved my file it failed.
Using the latest version
windows 10
using with c++
atom v1.15

[Arcanemagus]

Can you update to v2.0.0 and try again? Note that this package no longer bundles an out of date version of cpplint, so you will need to install it on your system yourself (pip install cpplint).

[JeffreyStrahm]

How do I open up the console where is dumps errors? I did that and now it's just saying check console for errors. Sorry for being a complete noob.

[Arcanemagus]

View -> Developer -> Toggle Developer Tools

[JeffreyStrahm]

[Arcanemagus]

Ah ha! That one's actually my fault 😞.

[Arcanemagus]

v2.0.1 should fix both the bugs in your screenshot there.

[JeffreyStrahm]

It works! No errors!

[Arcanemagus]

When #35 eventually gets fixed stuff like that should stop sneaking into releases 😞😛.