| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Maybe this should instead be:
... to write to `process.stdout` and `process.stderr`.
Sorry, something went wrong.
There was a problem hiding this comment.
Yep, I thought so too, but was waiting for this comment 😄
Sorry, something went wrong.
There was a problem hiding this comment.
Done
Sorry, something went wrong.
There was a problem hiding this comment.
Hmm, multiple places in this file refer to the standard output streams as just stdout, stderr. I think it's better to keep this paragraph unchanged for consistency.
Sorry, something went wrong.
There was a problem hiding this comment.
@mscdex your thoughts? I agree with both of you, to say, so not sure. From one point, it's OK to use stdout or "process stdout" because, it's how it is. Other point is let people understand that global console uses process.stdout and process.stderr Writable streams. Both points are good to me.
Sorry, something went wrong.
There was a problem hiding this comment.
I guess I don't really mind either way, as long as it's all consistent.
Sorry, something went wrong.
There was a problem hiding this comment.
@mscdex @silverwind Fixed.
Sorry, something went wrong.
Fix missing links. Fix styling of printf() - once #5073 lands, link to man page will be auto-generated. Fix several typos.
|
LGTM |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fix missing links. Fix styling of printf() - once #5073 lands, link to man page will be auto-generated. Fix several typos.