done
https://pharo.fogbugz.com/f/cases/16944/OSProcess-stdout-is-not-returned-back-to-pharo
On Sat, Nov 7, 2015 at 8:13 AM John Pfersich wrote:
>
>- Can you open a bug entry on http://pharo.fogbugz.com? This worked in
>Pharo 4.0.
>
>
> Sent from my iPad
>
> On Nov 6, 2015, at 01:30, Dimi
Can you open a bug entry on http://pharo.fogbugz.com? This worked in Pharo 4.0.
Sent from my iPad
> On Nov 6, 2015, at 01:30, Dimitris Chloupis wrote:
>
> looks like a vm problem after instruction of Thierry instead of
>
> wget -O- get.pharo.org/50+vmLatest | bash
>
> I did
>
> wget -O- get
Yes, that is normal. You are reading the output stream, and after it has
been read (up to EOF) it will be empty.
Glad it is working for you now :-)
Dave
> additionally if inspect output a second time , the stdout string is gone,
> so maybe it flushes / deletes it ? is this normal ?
>
> On Fri, N
additionally if inspect output a second time , the stdout string is gone,
so maybe it flushes / deletes it ? is this normal ?
On Fri, Nov 6, 2015 at 11:30 AM Dimitris Chloupis
wrote:
> looks like a vm problem after instruction of Thierry instead of
>
> wget -O- get.pharo.org/50+vmLatest | bash
>
looks like a vm problem after instruction of Thierry instead of
wget -O- get.pharo.org/50+vmLatest | bash
I did
wget -O- get.pharo.org/50+vm | bash
and now it works fine I can see the output with an inspection.
Looks like something changed in the vm that broke this.
On Fri, Nov 6, 2015 at 10:
good to know I am not the only one with this problem :) so how may I help
solving this problem ?
On Fri, Nov 6, 2015 at 10:11 AM john pfersich wrote:
> I tested what I posted on a fresh Pharo 4.0 image on OSX 10.10 (Yosemite)
> so it sounds like something's wrong in the trunk.
>
> On Thu, Nov 5,
I tested what I posted on a fresh Pharo 4.0 image on OSX 10.10 (Yosemite)
so it sounds like something's wrong in the trunk.
On Thu, Nov 5, 2015 at 10:38 PM, Dimitris Chloupis
wrote:
> It says I am using Cog 4.3.3
>
> I also used the code of John pfersich
>
> p :=(PipeableOSProcess waitForCommand
It says I am using Cog 4.3.3
I also used the code of John pfersich
p :=(PipeableOSProcess waitForCommand: 'ls') .
p output.
and it still returns an empty string while the process is
"a PipeableOSProcess on an ExternalUnixOSProcess with pid 769 on /bin/sh
(complete, normal termination with statu
Looks like what you want to do is:
p := (PipeableOSProcess waitForCommand: 'ls').
p output.
There's more information at
http://pharo.gemtalksystems.com/book/PharoTools/OSProcess/
On Thu, Nov 5, 2015 at 7:25 PM, David T. Lewis wrote:
> On Thu, Nov 05, 2015 at 10:22:31PM -0500, David T. Lewis w
On Thu, Nov 05, 2015 at 10:22:31PM -0500, David T. Lewis wrote:
>
> Or put "(Delay forSeconds: 1)" right before you do "p output"?
Sorry, I meant to say:
"(Delay forSeconds: 1) wait" right before you do "p output"?
Dave
On Fri, Nov 06, 2015 at 12:41:58AM +, Dimitris Chloupis wrote:
> hello David and thank you for your help and your detailed explanation.
>
> as I said I used
>
> p :=(PipeableOSProcess command: 'ls') . p output.
>
> and it just returns an empty string.
The way this should work is that p (an
hello David and thank you for your help and your detailed explanation.
as I said I used
p :=(PipeableOSProcess command: 'ls') . p output.
and it just returns an empty string.
Are there other ways to return the output of the terminal ?
On Fri, Nov 6, 2015 at 1:57 AM David T. Lewis wrote:
> On
On Thu, Nov 05, 2015 at 09:50:29PM +, Dimitris Chloupis wrote:
> So I try to understand how OSProcess work exactly to find why filetree
> seems not able to use it and generating the error I already reported
> earlier.
>
> Using something simple like
>
> OSProcess command:'pwd'
>
> works grea
I also tried
p :=(PipeableOSProcess command: 'ls') . p output.
and it just returns an empty string.
On Thu, Nov 5, 2015 at 11:50 PM Dimitris Chloupis
wrote:
> So I try to understand how OSProcess work exactly to find why filetree
> seems not able to use it and generating the error I already re
So I try to understand how OSProcess work exactly to find why filetree
seems not able to use it and generating the error I already reported
earlier.
Using something simple like
OSProcess command:'pwd'
works great , I have the terminal open and I can see the correct return
value of the command in
15 matches
Mail list logo
