Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use 'node-exit' for better windows support #172

Closed
Bartvds opened this issue Jan 17, 2014 · 10 comments
Closed

Use 'node-exit' for better windows support #172

Bartvds opened this issue Jan 17, 2014 · 10 comments

Comments

@Bartvds
Copy link

Bartvds commented Jan 17, 2014

Node.js has a known issue on windows with truncated stdout on process exit.

I have this now when using gulp within WebStorm.

The grunt team made a nice hack for it: I propose to use this in gulp: node-exit

@sindresorhus
Copy link
Contributor

strongly 👎, it destroys process.on('exit') for any loaded module.
Eg: https://github.com/sindresorhus/time-grunt/blob/master/time-grunt.js#L18

@Bartvds
Copy link
Author

Bartvds commented Jan 17, 2014

Yea, it is not ideal at all.

But stdout on windows is truncating (same as in the grunt issue), so this will come back again if gulp gets some more varied users (the issue was hot on grunt).

It is time it is fixed upstream in node itself. Bug is open for 2 years now.. 😞

@phated
Copy link
Member

phated commented Jan 21, 2014

Gulp doesn't have a goal to support Windows. I think this should be closed.

@yocontra
Copy link
Member

@phated to an extent - if an easy fix can be put in place that doesn't penalize others I would do it. node-exit breaks things on other OSes though apparently

@Bartvds
Copy link
Author

Bartvds commented Jan 21, 2014

Gulp doesn't have a goal to support Windows.

I can live without node-exit, it is a huge hack after all. With some luck this gets fixed upstream before 0.12.

But I'm sure this is a misunderstanding that Gulp doesn't support Windows? If you look at the known issue I mentioned you can see windows support in node.js is a real thing. Grunt can do it so I'd expect Gulp to do so too.

@thasmo
Copy link

thasmo commented Jan 21, 2014

Huh, why wouldn't gulp support Windows?

@phated
Copy link
Member

phated commented Jan 21, 2014

Calm down @Bartvds and @thasmo. As @contra said, Gulp will take patches for windows as long as they don't cause problems on other OSes. @robrich, a core contributor, uses windows, so it will continue to work for the foreseeable future. I was just stating that Gulp hasn't made it a goal to work 100% (like truncating stdout on exit) on windows over other OSes. This issue in particular should be fixed upstream.

Sorry for the confusion.

@robrich
Copy link
Contributor

robrich commented Jan 21, 2014

I agree. Though Windows support is near and dear to me (I think gulp fills the void left by nant and not filled by MSBuild) making everyone suffer isn't a good move. Let's push to have this resolved in node, not hacked around in gulp.

@sindresorhus
Copy link
Contributor

making everyone suffer isn't a good move

well, it's just putting the suffering on us developers having to support Windows :p

@Bartvds
Copy link
Author

Bartvds commented Jan 22, 2014

Cool, we'll see if node fixes this (one day..).

Re windows: if people not reinvent system stuff but use modules then things
work fine.. mostly :D

2014/1/21 Sindre Sorhus notifications@github.com

making everyone suffer isn't a good move

well, it's just putting the suffering on us developers having to support
Windows :p


Reply to this email directly or view it on GitHubhttps://github.com//issues/172#issuecomment-32967986
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants