From: Marc Hartstein <marc.hartstein@alum.vassar.edu>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [PATCH] mutt-style pipe to interactive process support
Date: Sat, 26 Jun 2010 12:37:06 -0400 [thread overview]
Message-ID: <1277569950-sup-2290@cabinet> (raw)
In-Reply-To: <1277569807-12085-1-git-send-email-marc.hartstein@alum.vassar.edu>
[-- Attachment #1.1: Type: text/plain, Size: 771 bytes --]
Code review would be highly appreciated on this one. I did some research
and checking and I'm fairly confident that I got the multiprogramming
aspects correct, but I haven't done much with forked processes before,
so I'd appreciate another set of eyes on it.
As always, I'm receptive to style review to best integrate with the
predominant Sup programming style as well.
The primary motivation for this patch is that the one thing I've missed
most in moving from mutt is being able to use urlview to quickly open
urls in my browser. While urxvt helps me with short urls, anything
longer than my current viewport line gets broken in a way urxvt can't
detect, so I decided it was time to make the pipe command more powerful.
I've left the old code pathways fully intact.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-06-26 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 16:30 Marc Hartstein
2010-06-26 16:37 ` Marc Hartstein [this message]
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=1277569950-sup-2290@cabinet \
--to=marc.hartstein@alum.vassar.edu \
--cc=sup-talk@rubyforge.org \
/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