Buffer stderr and stdout before triggering callbacks #44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, whenever the compile_command outputs data on stdout or stderr the corresponding
on_stdout
oron_stderr
is called. This results in multiple (at least 5 for even one compilation error) calls to those functions which in turn do some work parsing errors. Addingstdout_buffered
andstderr_buffered
tovim.fn.jobstart
will wait until they finish writing to those descriptors, reducing the calls toon_stdout
andon_stderr
to at most one.