Allow setting different maxBuffer
values for stdout
/stderr
#966
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.
This starts implementing #930, starting with the
maxBuffer
option.This is the beginning of a series of PRs to add the following syntax, to allow some options to have different values for
stdout
andstderr
.The other options are
verbose
(which is the most useful one in that respect, since users might wantstderr
to be more verbose thanstdout
during debugging),stripFinalNewline
,buffer
,lines
andencoding
. This PR adds the base for the next PRs, so it is bigger.