Hello all again. I updated the VM, but the error still appears. It appears
only the first time I run my tests. I DO have the latest version of
OSProcess-AIO. Any thoughts?
Thanks!
El vie., 1 de may. de 2015 a la(s) 6:38 p. m., Demian Schkolnik <
demianschkol...@gmail.com> escribió:
>
Thank you phil & Davorin. I'll try using a newer VM and see how that works.
El vie., 1 de may. de 2015 a la(s) 6:29 p. m., Davorin Rusevljan <
davorin.rusevl...@gmail.com> escribió:
> On Fri, May 1, 2015 at 11:54 PM, Demian Schkolnik <
> demianschkol...@gmail.com> w
feasibility, I'd start with a single shell
>> script outputting text at intervals like this...
>> "test.sh"
>> for VARIABLE in 1 2 3 4 5 .. N
>> do
>> echo $VARIABLE
>> sleep 2
>> done
>>
>>
>> and in P
>
> However just wildly guessing, are you wanting to get output from a long
> running command without blocking the Pharo UI?
> In that case, what about...
> [ *stringVar := (PipeableOSProcess command: 'echo...') output ]
> fork. *
> *?*
> *cheers -ben
Hello everyone.
I have the following question. I have a specific 'echo ...' command, which
I send to the linux console via " OSProcess command:'echo ... ' ".
This echo command, when executed on the native linux console, stands by
until it receives some message.
Following this, I have to execute a
Greetings.
I have to do a bunch of tests, where the initial set up is quite costly
(launching ROS system and a bunch of nodes). Therefore, I don't want to set
it up each time before a test (like with the standard setUp function). How
can I make it so that the setUp function is called only once ove
