From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] [PATCH] Pipe message/attachement to shell command
Date: Mon, 26 Nov 2007 20:57:05 +0000 [thread overview]
Message-ID: <1196110544-sup-3133@tomsk> (raw)
In-Reply-To: <1195032303-sup-7083@tomsk>
On 14.11.2007, Marcus Williams wrote:
> Ok, heres the new one. I think in the pipe to command case, the
> session gem is probably the best way to go (although I've not use it
> here) because it handles the blocking problems for you.
Here we go again. Attached is the shell patch (pipe to follow) as a
patch to bin/sup instead of in the scroll mode.
Marcus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: shell-patch
Type: application/octet-stream
Size: 1221 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071126/bd47d15c/attachment-0001.obj
next prev parent reply other threads:[~2007-11-26 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 15:33 Marcus Williams
2007-11-12 17:55 ` William Morgan
2007-11-12 22:06 ` Marcus Williams
2007-11-13 11:58 ` Marcus Williams
2007-11-14 9:40 ` Marcus Williams
2007-11-26 20:57 ` Marcus Williams [this message]
2007-11-26 21:01 ` Marcus Williams
2007-12-10 6:24 ` 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=1196110544-sup-3133@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