From: Zachary Scott Date: 2013-10-04T12:41:20+02:00 Subject: [ruby-core:57664] Re: Suggestion for CreateProcess flags with rubyw on windows --Apple-Mail=_A42D7435-724C-48D8-B57C-056382BEEA65 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 I would just open a ticket, this will give you a much better chance at = feedback. On Oct 2, 2013, at 5:35 PM, James French = wrote: > Hi, > =20 > I=92ve spent some time looking into the feasibility of using rubyw in = my code and at first glance it looks ideal. However there are a lot of = console windows flashing up when I run external processes using = Open3::popen3 (because I want to capture their stdout and stderr). I = believe that creating a process without CREATE_NO_WINDOW in rubyw is a = bug, as the whole point of rubyw is that it doesn=92t pop up a console. > =20 > If there is agreement I=92m happy to file a bug report/submit a patch. > =20 > Cheers, > James --Apple-Mail=_A42D7435-724C-48D8-B57C-056382BEEA65 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252

I would just open a = ticket, this will give you a much better chance at = feedback.

On Oct 2, 2013, at 5:35 PM, = James French <James.French@naturalmotion.= com> wrote:

Hi,
I=92ve spent some = time looking into the feasibility of using rubyw in my code and at first = glance it looks ideal. However there are a lot of console windows = flashing up when I run external processes using Open3::popen3 (because I = want to capture their stdout and stderr). I believe that creating a = process without CREATE_NO_WINDOW in rubyw is a bug, as the whole point = of rubyw is that it doesn=92t pop up a console.

If = there is agreement I=92m happy to file a bug report/submit a = patch.