say it on the mailing-list and damien takes into account the result.
Stef
> By the way, what is the proper way to propose changes to the dev
> image script?
>
> On Tue, Oct 27, 2009 at 3:57 PM, Niko Schwarz
> wrote:
>> My image is indeed still on version damiencassou.33. I marked the bug
>> a
On Tue, Oct 27, 2009 at 4:00 PM, Niko Schwarz
wrote:
> By the way, what is the proper way to propose changes to the dev image script?
Talk about them on the mailing list and add me on CC. Also, open an
issue in the tracker and assign it to me.
--
Damien Cassou
http://damiencassou.seasidehosting
By the way, what is the proper way to propose changes to the dev image script?
On Tue, Oct 27, 2009 at 3:57 PM, Niko Schwarz
wrote:
> My image is indeed still on version damiencassou.33. I marked the bug
> as 1.0 in the bugtracker
> (http://code.google.com/p/pharo/issues/detail?id=1351) hoping th
My image is indeed still on version damiencassou.33. I marked the bug
as 1.0 in the bugtracker
(http://code.google.com/p/pharo/issues/detail?id=1351) hoping that it
will be integrated in the next 1.0 dev image, as the image is hardly
usable without the fix.
Cheers,
Niko
On Tue, Oct 27, 2009 at 3
Niko,
What is the version of OCompletion in the image?
I thought the fix in Ocompletion-RomainRobbes.36.mcz solved that issue.
If you are indeed using that version, I'll have a look at your fix.
Otherwise, it is just a matter of time before the
latest version of OCompletion is used instead of t
Hi list,
in the most recent dev image (9.10.5), OCompletion is broken for me.
I lost my reproducible test case, but the gist was that sometimes when
OCompletion had no idea which type a temporal variable would be, you
were unable to insert code behind that variable, because if you tried,
a debugg
