on linux I used to have a BASH shell "wrapping" script to address this redirect snaffu in a pinch with other interpreters ...
Does that "ring a bell" with someone as a quick work-around ? My memory can be such a pain and I am on an old XP laptop just now ... I am quite sure I had to launch from BASH ... within Bash On 28 July 2014 11:46, François Stephany <tulipe.mouta...@gmail.com> wrote: > > $ pharo Pharo-30852.image > /tmp/test.log > > Outputting somethind to stdout results in: > "FileWriteError: File stdout is closed" > > * Arch Linux > * Pharo 30852. > > $ pharo --version > > 3.9-7 #1 Thu May 15 18:29:30 CEST 2014 gcc 4.6.3 [Production ITHB VM] > NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 May 15 2014 > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 May 15 2014 > https://github.com/pharo-project/pharo-vm.git Commit: > ed4a4f59208968a21d82fd2406f75c2c4de558b2 Date: 2014-05-15 18:23:04 +0200 > By: Esteban Lorenzano <esteba...@gmail.com> Jenkins build #14826 > Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 > UTC 2012 i686 i686 i386 GNU/Linux > > > Did I miss something? > >
