pharo Pharo.image --list will give you the command lines available, then
pharo Pharo.image aCommand --help will give you the subcommands possible in your case, you want something like this: pharo Pharo.image eval “99 factorial” cheers, Esteban ps: this questions are more for the pharo-users list than pharo-dev :) > On 27 Apr 2016, at 20:04, [email protected] > <[email protected]> wrote: > > there should be a handler name in there. > > Like in pharo-ui Pharo.image st somefile.st <http://somefile.st/> > st is the handler. > as is eval or config or your own. > > Check subclasses of CommandLineHandler including class side. > > Phil > > On Apr 27, 2016 6:50 PM, "blake watson" <[email protected] > <mailto:[email protected]>> wrote: > Hi-- > > I've seen this come up several times (and it's in "Deep") but I can't seem to > actually make Command Line Arguments work. > > If I do (this is under Windows, but I set up a fresh Linux just to ensure it > wasn't a Windows quirk): > > Pharo.exe Pharo4.0image 99 > > Pharo comes up with "Command line handler failed". I see in the stack trace > that the "99" comes in as an orderedCollection. And if I do: > > Pharo.exe Pharo4.0image 99 100 101 > > I get an orderedCollection with 99, 100 and 101, which is what I'd expect. In > fact, it would be perfect if it didn't crash and put those values somewhere, > like, I don't know, CommandLineArguments' arguments variable? =) > > So, I'm obviously not getting something here. How do I make simple parm > passing work? > > Also, I note that: > > Pharo.exe 99 100 101 > > Brings up Pharo with the default image but swallows the 99, which seems odd. > I'm guessing that it looks for a 99.image and not finding it, ignores the > parameter and loads the default image. But it'd be smarter at that point to > put the 99 back, I think. > > ===Blake=== >
