If it was due to transferring of a large result from pylint, then the laptop would be affected as well. The only thing special about running it in Atom that I can think of is that it does a few extra things to fix odd edge cases on certain OS's.
You could try cutting all that out of the time and starting the timer right before this:
That's the time it takes to spawn the command and get the results back, any extra time on top of that is preparing to run the command in Atom and shuffling the result around and processing it.
That makes no sense 😕.
If it was due to transferring of a large result from
pylint
, then the laptop would be affected as well. The only thing special about running it in Atom that I can think of is that it does a few extra things to fix odd edge cases on certain OS's.You could try cutting all that out of the time and starting the timer right before this:
https://github.com/steelbrain/exec/blob/48910bbba76495bab2418edbebc0f9389a56867e/src/index.js#L33
And ending it here:
https://github.com/steelbrain/exec/blob/48910bbba76495bab2418edbebc0f9389a56867e/src/index.js#L51
That's the time it takes to spawn the command and get the results back, any extra time on top of that is preparing to run the command in Atom and shuffling the result around and processing it.