Suppress new proccess output

[fuadsaud]

Didn't find a way to suppress or redirect the STDOUT of new proccess.

[copiousfreetime]

Can you show me an example of what you mean?

[fuadsaud]

Sure! Take this example:

Launchy.open 'http://github.com'

Google Chrome / Chromium are going to print "Created new window in existing browser session." to STDOUT. I wish I could be able to redirect the output of the process to somewhere else, (like /dev/null).

[copiousfreetime]

Hrm, it looks like this may be platform dependent. I do not see this on OSX.

jeremy@stiletto:~ ruby-1.9.3-p194 % cat x.rb
require 'launchy'
puts "Launchy version #{Launchy::VERSION}"
Launchy.open 'http://github.com'

jeremy@stiletto:~ ruby-1.9.3-p194 % ruby -rubygems ./x.rb 
Launchy version 2.1.2
jeremy@stiletto:~ ruby-1.9.3-p194 % 

jeremy@stiletto:~ ruby-1.9.3-p194 % rvm use 1.8.7
Using /Users/jeremy/.rvm/gems/ruby-1.8.7-p358
jeremy@stiletto:~ ruby-1.8.7-p358 % ruby -rubygems ./x.rb 
Launchy version 2.1.2
jeremy@stiletto:~ ruby-1.8.7-p358 %

What is the platform you are on and your launchy version?

[fuadsaud]

Ubuntu 12.04 LTS 64bit 3.2.0-29

Launchy 2.1.2

[copiousfreetime]

Thanks, I was able to replicate it now. It appears to possibly be an Ubuntu only issue, or maybe a linux only issue. I think I'll attempt to figure out why it is happening first, and then once i understand that, I'll put in an output redirection or an appropriate flag to the launch command to deal with it.

Thanks for finding this bug!

[sferik]

Has there been any progress on this issue in the past 5 months? It is causing issues for users of one of my gems: sferik/t-ruby#77. If no one else is actively working on this, I can look into it, but it will be harder for me to reproduce, since I don't run Ubuntu. I guess I can spin up a Vagrant box.

[fuadsaud]

hum, I don't think Ubuntu is needed in this case. Is just a simple STDOUT redirection. Not sure about Windows support however.

[sferik]

@copiousfreetime, thanks for fixing this! Very much looking forward to the next release.

[copiousfreetime]

New release pushed v2.2.0

[david-s-svedberg]

Still experiencing the issue in version 2.4.3 running on Ubuntu 14.04. As before, when executing Launchy.open(url) it opens the url in chrome but I get an output to stdout "Created new window in existing browser session."

[nunosilva800]

Same here, it's kinda annoying...

[copiousfreetime]

@david-s-svedberg @Onumis At the moment, launchy should be capturing all its stdout/stderr in the child process that launches chrome, and only displaying it if there was an exception. The relevant code is https://github.com/copiousfreetime/launchy/blob/master/lib/launchy/detect/runner.rb#L133-L141.

Feel free to put some debugging into there and see if the same thing occurs. The easy burn test would be to explicitly add $stdout.close and $stderr.close instead of saving them off to the side in StringIO and see if that alleviates your issue.

If, when doing this, you no longer see Created new window in existing browser session. then there is something going on with the file descriptors that I'm unfamiliar with.

If you still see the output from chrome, then I'm not sure where that output is coming from or how it is getting to your console.

In any case, if someone has a Vagrant file handy that I can use to setup a system in the same manner you have, that would be helpful.