Edmund R. MacKenty wrote:
Rob van der Heij writes:
On 10/13/05, Alan Altmark <[EMAIL PROTECTED]> wrote:
to stdout itself. (I do this all the time in REXX execs - handle the
return codes I can deal with myself and dump to the console if I don't
recognize it. Is Linux so different?)
Yep. You're missing CMS Pipelines and maybe REXX stems. As the
examples show you must redirect output to a temporary file (and deal
with the fact that some commands produce different output when
redirected) and then read the file back in to see what was
there.That's not elegant. My `vmcprc` was as close as I could get.
Actually, you can capture the output of any command into a shell variable,
While that is true, as I've popinted out before, hiding messages from
suers is evil. Sooner or later, something will break, and the user will
need information being hidden.
That is why I suggested a different file descriptor, and Alan was
agreeing that, with a small proviso, that's okay.
Way back, I showed how that "different file descriptor" can be created
and accessed in shell scripts.
The vmcprc example involved sending stdout to an environment variable,
and this I think is *bad*.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
