From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: [9fans] rx - wot no stderr?
Date: Wed, 17 Jan 2007 17:14:01 +0000 [thread overview]
Message-ID: <2c5a7c3362eeff4e33cf9c16f07a6149@quintile.net> (raw)
I was surprised to find plan9's implementaion of
rx(1) and rexexec(8) don't support a seperate socket
for stderr out of the remote application.
I can see that it is not that great, but somtimes
when doing (from the manpage):
eqn paper | rx kremvax troff -ms | rx deepthought lp
It would be nice to see your troff error messages
onscreen rather than having to collect them from the
printer.
Was the decision not to implement stderr strongly
felt, or just a case of "Its not worth the complexity"?
-Steve
next reply other threads:[~2007-01-17 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 17:14 Steve Simon [this message]
2007-01-19 12:32 ` Gorka guardiola
2007-01-19 13:07 ` erik quanstrom
2007-01-19 14:35 ` Steve Simon
2007-01-19 22:17 ` erik quanstrom
2007-01-20 1:15 ` Steve Simon
2007-01-20 1:34 ` erik quanstrom
2007-01-24 21:03 ` rog
2007-01-21 7:06 ` ron minnich
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=2c5a7c3362eeff4e33cf9c16f07a6149@quintile.net \
--to=steve@quintile.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).