Nope. I upgraded to 1.5.1.1166 and when I change the .rb file extension to use rubyw.exe instead of ruby.exe it still fails:
"c:\ruby\bin\ruby.exe" "%1" %* to "c:\ruby\bin\rubyw.exe" "%1" %* ============================================ What happens is that after it opens the browser (using ie-new-process) nothing is executed in the script after that point, it just stops. I put in a "system 'echo test > file.txt'" command, to see if it is even moving past the part where it opens the browser, and it doesn't execute it. It just terminates. I am guessing that since stderr, stdin, stdout are all disabled for rubyw.exe, that is why I get nothing, just terminates... Does it have something to do with the fact that ie-new-process puts the process id to stdout? Maybe that is what is crashing it when running under rubyw.exe? If I put it back to use ruby.exe, instead of rubyw.exe, the code works perfectly... (But I have that ruby console window sitting there, which is a little bit of an annoyance, especially if you have several scripts running...) _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
