Re: capture stdout and stderr

2018-05-29 Thread Catonano
2018-05-27 19:26 GMT+02:00 Thomas Danckaert : > From: Stefan Israelsson Tampe > Subject: Re: capture stdout and stderr > Date: Thu, 24 May 2018 15:25:51 +0200 > > I think that your code whould work but doesn't because string ports are >> not file ports and system comman

Re: capture stdout and stderr

2018-05-27 Thread Thomas Danckaert
From: Stefan Israelsson Tampe Subject: Re: capture stdout and stderr Date: Thu, 24 May 2018 15:25:51 +0200 I think that your code whould work but doesn't because string ports are not file ports and system commands pipes out to file ports. 'open-input-pipe' uses 'sc

Re: capture stdout and stderr

2018-05-26 Thread Thomas Danckaert
From: Catonano Subject: Re: capture stdout and stderr Date: Sat, 26 May 2018 12:24:11 +0200 The first observation is that in the first case, you close the port cotaining the error _prior_ to attempting reading from the port In the second case, you attempt reading from the port AND THEN you

Re: capture stdout and stderr

2018-05-26 Thread Catonano
2018-05-24 10:10 GMT+02:00 Thomas Danckaert : > Hi Guilers, > > I want to run an external process, and capture both its stdout and stderr > output streams. I didn't find an easy way to get a port for an external > process' stderr, other than wrapping the call to the process in > "with-error-to-po