can't connect to STDOUT windows wsl2 pengwin distro

[masinter]

[masinter]

can't connect to STDOUT? doesn't seem to produce go through. I can

(setq stdin (OPEN "{unix}/dev/stdin" :direction :input))

and get an input stream from STDIN. (it should probably default the EXTERNAL-FORMAT the same way the PROCESS streams do.)

But (setq stdout (open "{unix}/dev/stdout" :direction :output :if-exists :append))
seems to work, but no output appears.

Using, say, CL:OPEN --

(setq stdin (open "{unix}/dev/stdin" :direction :input))
(read stdin)

This reads ASCII (or UTF-8) input independent of the keyboard setup so you can write a headless medley server trivially.

Originally posted by @nbriggs in #334 (comment)

[nbriggs]

It appears when you flush or close the output. It’s all buffered by the OS.

[masinter]

I'm still having trouble with output in the meanwhile I can write a file.

[nbriggs]

So it works sometimes ...?

[masinter]

... depending on which OS you're running? (WSL2 here)

[nbriggs]

Does WSL2/pengwin have "truss", or some equivalent that should trivially show what actual error the close system call generated?

[masinter]

sotruss… I’ll give it a try --LarryMasinter.netOn Apr 8, 2023, at 6:12 PM, Nick Briggs ***@***.***> wrote: Does WSL2/pengwin have "truss", or some equivalent that should trivially show what actual error the close system call generated? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[nbriggs]

Try "strace" if it is installed -- "sotruss" traces shared library calls not system calls.