This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7.3k
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7.3k
Assigning to process.stdout
has no effect
#1878
Comments
I think its because your simply updating the property on process, your not ACTUALLY redirecting the FD 1 to /dev/null. |
@aikar I know the way around it (there are few ways, actually). It's more about the fact that it worked in node v0.4 (I've edited issue description to clarify it) |
Not really a bug. process.__defineGetter__('stdout', function() {
return your_object;
}); |
But maybe worth documenting on https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6 ! |
@bnoordhuis Thanks for a clarification and sorry for the unneeded buzz. Sure, I'll document it. |
Cool, thanks. |
mmalecki
added a commit
to mmalecki/vows
that referenced
this issue
Oct 13, 2011
In node v0.5.x `process.stdout` is a getter, so assigning to it makes no difference (see nodejs/node-v0.x-archive#1878 - thanks @bnoordhuis).
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm not sure if it's a bug or a desired behavior. I've tried bisecting, but many revisions failed to build on my system, so git left me in the middle of nowhere.
Doing:
has no effect on node v0.5.x (
console.log
s andprocess.stdout.write
s are still being printed), but works on node v0.4.x.If that's a real issue, I'll provide a test case.
The text was updated successfully, but these errors were encountered: