Isn't that something complementary to pharo. Why have the tools a different name??? I think pharo should be usable as scripting engine. And that means files should begin with #! /usr/bin/env pharo Norbert
Am 22.10.2016 um 13:41 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
On 22 Oct 2016, at 12:41, Dimitris Chloupis <kilon.alios@gmail.com> wrote:
This link may interest you command line people , it basically what I proposed as an idea early on
yes, Santi is working a lot on it so I think they are going to release it very soon :)
Esteban
On Sat, 22 Oct 2016 at 13:20, Dimitris Chloupis <kilon.alios@gmail.com> wrote: I was replying to Thierry saying that we had issues with Pharo mixing metarepo6 with metarepo5
On Sat, 22 Oct 2016 at 13:11, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 22 Oct 2016, at 12:00, Dimitris Chloupis <kilon.alios@gmail.com> wrote:
Didn't Esteban fixed metarepo ? I think I remember him saying that he did.
fixed in what sense?
Esteban