[Cuis-dev] OSProcess standard output

[Jon Raiford]

Hi Hilaire,

I ran into this problem as well and implemented it via FFI. It's much lighter weight than the full OSProcess package (that I only learned about after I implemented it). This was from a few years ago. I'll see if I can find it. If not, it is quite simple to call into the glibc library for both functions and shared variables.


Jon Raiford

LabWare Holdings | 3 Mill Road, Suite 102, Wilmington, DE 19806

Tel: (302) 658-8444 ext. 121   |   Email: raiford at labware.com



From: Cuis-dev <cuis-dev-bounces at lists.cuis.st> on behalf of Hilaire Fernandes via Cuis-dev <cuis-dev at lists.cuis.st>
Date: Sunday, March 15, 2026 at 3:33 PM
To: cuis-dev at lists.cuis.st <cuis-dev at lists.cuis.st>
Cc: Hilaire Fernandes <hfern at free.fr>
Subject: Re: [Cuis-dev] OSProcess standard output


Hi Dave,

Thanks for the tips. I will check it out.

In the meantime I tried this with OSProcess (thanks Nicola for your cookbook), but its seems the output stream must be a file, which I would like to avoid. Am I correct?

| proc d outStream |
d := Delay forMilliseconds: 50.
outStream := ReadWriteStream on: String new.
proc := UnixProcess
    forkJob: '/usr/bin/bash'
    arguments: {'-c'. 'ls -l'}
    environment: nil
    descriptors: {nil. outStream.nil}.
[proc runState == #complete] whileFalse: [d wait].
outStream contents.

Is CommandShell the only way to have standard output with going through a file on disk?

Thanks

Hilaire

--
http://mamot.fr/@drgeo<http://mamot.fr/@drgeo>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20260317/38987f7b/attachment.htm>