doc: clarification for maxBuffer and Unicode output#6030
doc: clarification for maxBuffer and Unicode output#6030jasnell wants to merge 1 commit intonodejs:masterfrom
Conversation
|
TBH, it seems kind of pointless to me - most child processes will simply ignore it - and it's already perfectly possible to set an environment variable. I don't really see why this should be in core. |
|
Fair enough. What do you think about the docs change, however? |
|
The change to the documentation LGTM if you remove the reference to |
ba28b95 to
b693bab
Compare
b693bab to
1f02970
Compare
|
@bnoordhuis ... updated so that it's just the documentation changes. Also cleaned up some errant line-wrapping issues and end-of-line-whitespace. PTAL |
|
LGTM |
1 similar comment
|
LGTM |
Clarify caveats on `maxBuffer` with regards to Unicode output. Refs: nodejs#1901
1f02970 to
b968cc3
Compare
|
Landed in ad2df3a |
|
@jasnell lts? |
|
@jasnell lts? |
|
+1
|
|
@jasnell not landing cleanly, would you like to backport? |
|
will do |
|
ping @jasnell |
|
Thanks for the reminder, will do this week. |
|
@jasnell added don't land. Feel free to still open a backport PR |
Pull Request check-list
make -j8 test(UNIX) orvcbuild test nosign(Windows) pass withthis change (including linting)?
test (or a benchmark) included?
existing APIs, or introduces new ones)?
Affected core subsystem(s)
doc
Description of change
Clarify caveats on
maxBufferwith regards to Unicode output.Refs: #1901