On Mon, 6 Aug 2018 at 12:18, Damien Pollet <damien.pollet@gmail.com> wrote:
Yes, they do, at least on my macOS.
I have some doubt about #stdioIsAvailable though⦠before there was a possible value of 4 (cygwin terminal) for the file descriptor type, which is now out of the tested range, is that intentional
Yep. Pharo can't write to a cygwin terminal since it uses the Windows Read/WriteConsole() functions. cygwin terminals are actually written to through pipes, and we can get the pipe information, and thus determine it is a cygwin terminal. But that's it for now. Cheers, Alistair
On Mon, 6 Aug 2018 at 12:00, Guillermo Polito <guillermopolito@gmail.com> wrote:
Damien,
Could you check that at least the proposed image-side changes fix your problem for *nixes?
On Sat, Aug 4, 2018 at 7:13 PM Sean P. DeNigris <sean@clipperadams.com> wrote:
Alistair Grant wrote
Tracking issue: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/274 The issue above is for the VM changes.
The issue for image changes is: https://pharo.fogbugz.com/f/cases/22296/Stdio-file-creation-fixes
Thanks for looking into this, Alistair! Few are brave enough to dive into these dark corners of the system ;-)
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
--
Guille Polito
Research Engineer
Centre de Recherche en Informatique, Signal et Automatique de Lille
CRIStAL - UMR 9189
French National Center for Scientific Research - http://www.cnrs.fr
Phone: +33 06 52 70 66 13
-- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet