[x3d-public] Node.exe on windows 10 with bash.exe

[yottzumm at gmail.com]

The actual solution was to add

process.exit();

To the end of my program.  This suits me well.

Thanks for your assistance.

John

Sent from Mail for Windows 10

From: Cecile Muller
Sent: Thursday, February 23, 2017 11:12 AM
To: John Carlson
Subject: Re: Node.exe on windows 10 with bash.exe

I'm glad you found a solution :)

2017-02-23 16:54 GMT+01:00 <yottzumm at gmail.com>:
It now appears to be more about node.exe now that they have people looking into it. (Good news)   We may get some traction, but they’ve tried to solve this problem before.   It may interfere with other usecases.
 
It appears to be about blocking stderr and stdout.
 
 
Piping works fine with other programs, for example jjs.  There are some tricky programs that have to use winpty. If you just use node, you will get winpty node.exe as an alias from the shell.  node.exe is the way to go.
 
You can try this quick program too:
 
(node.exe fillbuffer.js && node.exe fillbuffer.js) | node.exe read.js
 
Where read.js is:
 
process.stdin.on('data', console.log);
process.stdin.on('end', console.log);
 
Much simpler than the piping I came up with, and much more node centric. And all bash and node.js 😊

Thanks to the node.js team for their insights.
 
John
 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170224/671309e5/attachment.html>