noreply at rubyforge.org
2009-Jan-10 11:27 UTC
[Win32utils-devel] [ win32utils-Feature Requests-23514 ] Possibility to get exitstatus from app ran by open3
Feature Requests item #23514, was opened at 2009-01-10 12:27 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=414&aid=23514&group_id=85 Category: win32-open3 Group: None Status: Open Resolution: None Priority: 3 Submitted By: Roman Zawada (zwadar) Assigned to: Nobody (None) Summary: Possibility to get exitstatus from app ran by open3 Initial Comment: Hi, because bug [#23356] http://rubyforge.org/tracker/index.php?func=detail&aid=23356&group_id=85&atid=411 is rather unsolvable, maybe would be possible to introduce some other way to catch proper existatus on Windows machines with Open3 library? I wrote this to bug [#23356] comments, but I pressume no one has read it :-) Saddly lack of exitstatus is reason wy I can''t use open3 for now. I''m using http://groups.google.com/group/comp.lang.ruby/msg/c0e7fc74641b9a50 for getting stderr and exitstatus (little bit modyfied, because this script catshes exitstatus of executed ruby script, not from executed app from it), but i think this is realy ugly solution of the problem. Thanks ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=414&aid=23514&group_id=85
Berger, Daniel
2009-Jan-12 14:35 UTC
[Win32utils-devel] [ win32utils-Feature Requests-23514 ]Possibility to get exitstatus from app ran by open3
Quick followup...> Hi, > because bug [#23356] > http://rubyforge.org/tracker/index.php?func=detail&aid=23356&g > roup_id=85&atid=411 > is rather unsolvable, maybe would be possible to introduce > some other way to catch proper existatus on Windows machines > with Open3 library? > I wrote this to bug [#23356] comments, but I pressume no one > has read it :-) Saddly lack of exitstatus is reason wy I > can''t use open3 for now. > I''m using > http://groups.google.com/group/comp.lang.ruby/msg/c0e7fc74641b9a50 > for getting stderr and exitstatus (little bit modyfied, > because this script catshes exitstatus of executed ruby > script, not from executed app from it), but i think this is > realy ugly solution of the problem.This was resolved in win32-open3-0.2.7, which is now available. Regards, Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.