17:20 <jA_cOp> Is there a nice way with the standard library to run a subprocess until it finishes, and capture its stdout *and* exit code to variables? I'm using `(with-output-to-string (lambda () (system* ...)))` which evaluates to the standard output, but then I have to handle the exit code inside the lambda, and if I wanted stderr it would be a similar story

19:29 <winny> jA_cOp; subprocess, though you could simplify it by lifting the code into a utility procedure. a contrived example in a simple tool i wrote https://github.com/winny-/ssh-hack/blob/9e8099a385fed26def70690279ad9d4ff3a097d0/ssh-hack.rkt#L79-L89

19:31 <winny> i think system kind of maps to the system(3) libc thing, it's not very flexible. https://www.gnu.org/software/libc/manual/html_node/Running-a-Command.html#Running-a-Command

19:39 <winny> another option https://docs.racket-lang.org/reference/subprocess.html?q=system#%28def._%28%28lib._racket%2Fsystem..rkt%29._process%29%29

19:39 <rudybot> https://teensy.info/yAx5ETtYin

21:01 <jA_cOp> Thanks a lot winny ; that's a good example, I think I'll use subprocess!

21:06 <jA_cOp> I guess the only adjustment I would need is to call `(port->string stdout)` to get the stdout as a string after the wait and status check