if you do something like this:
| p d |
p := (PipeableOSProcess command: 'touch files.txt').
p keepInitialStdOutOpen: true.
d := Delay forMilliseconds: 250.
d wait.
[Transcript show: (p next: 300); flush. p atEnd] whileFalse: [d wait].
Transcript show: (p errorUpToEnd).
p closeOutput.
then you'll
I share the impressions of Cyril here. The relation between the "P" and
the rest of the "illar" seems too much disproportionate. The second
pillar doesn't help with readability and I know about Pharo things kind
of "sea" related, but I would try to focus more on known pillars like
[1] or [2] as
Mariano,
I have the same thing in a freshly installed image. I couldn't say I can
reproduce it at will but now it happened in two different images. Anything
special I should look up?
Norbert
> Am 11.03.2016 um 13:07 schrieb Mariano Martinez Peck :
>
> Hi Norbert,
>
> I have never seen that i
Hello,
I am working with Roassal and trying to write a cell-layout builder that
uses RTPieBuilders internally as its nested objects. The nesting docs cover
nesting RT elements, but not builders. The composition docs cover composing
builders, but not nesting them. I have a partial solution, but it
On 03/03/16 09:23, stepharo wrote:
for the mooc I would like have a list of how to that students should
look in the system and implement.
The idea is to show to the participants that Pharo is open and that they
can find information.
At #saner16 there was a talk about type hints in argument name
