Hi,
I'm trying to figure out how to capture the standard error of a piped process
without resorting to forking an additional sh process.
Any hint?
Thanks in advance,
Jorge
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi Jorge,
> I'm trying to figure out how to capture the standard error of a piped
> process without resorting to forking an additional sh process.
If it is enough to redirect it to a file, you might enclose the pipe
call with 'err'. The following appends the message to "error.log":
(err "+err
