From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] patch: execute shell command
Date: Mon, 12 Nov 2007 15:35:34 +0000 [thread overview]
Message-ID: <1194881637-sup-5906@tomsk> (raw)
In-Reply-To: <1194843828-sup-7014@timmy>
On 12.11.2007, Eyal Oren wrote:
> > I like this functionality but the session gem seems like it's overkill
> > here. Is there a reason to use it instead of just something like
> > output = `#{cmd}`
> I also wanted to catch error output, to find out if an unexisting command was
> invoked, and I didn't know how to do that with ``?
Shouldnt this be possible with open3? The only problem is that open3
is unix only (in std ruby). I think there is a win32 open3 gem though.
Marcus
next prev parent reply other threads:[~2007-11-12 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 15:47 Eyal Oren
2007-11-12 4:13 ` William Morgan
2007-11-12 5:05 ` Eyal Oren
2007-11-12 15:35 ` Marcus Williams [this message]
2007-11-12 16:59 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1194881637-sup-5906@tomsk \
--to=marcus-sup@bar-coded.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox