or simply read the Class comments in the image, that's basically the content
shown by all the --help stuff ;)

And yes it will be announced in the 2.0 release message :)

On 2013-03-08, at 14:57, Sven Van Caekenberghe <[email protected]> wrote:
> On 08 Mar 2013, at 14:50, Torsten Bergmann <[email protected]> wrote:
> 
>> Sven wrote:
>>> The last couple of days I have been using the new command line tools and 
>>> zero conf scripts for real and I must say that I am >truly impressed and 
>>> happy. 
>>> 
>>> The save, printVersion, eval, st, config and test handlers are a joy to 
>>> work with. The terminal colours add a nice polish.
>> 
>> Any documentation on it, blog posts or pharocasts available?
>> 
>> Thx
>> Torsten
> 
> It is self-documenting ;-)
> 
> $ ./vm.sh Pharo.image --help
> 
> Usage: [<subcommand>] [--help] [--copyright] [--version] [--list]
>       --help       print this help message
>       --copyright  print the copyrights
>       --version    print the version for the image and the vm
>       --list       list a description of all active command line handlers
>       <subcommand> a valid subcommand in --list
>       
> Documentation:
> A DefaultCommandLineHandler handles default command line arguments and 
> options.
> The DefaultCommandLineHandler is activated before all other handlers. 
> It first checks if another handler is available. If so it will activate the 
> found handler.
> 
> 
> $ ./vm.sh Pharo.image --list
> 
> Currently installed Command Line Handlers:
>    st              Loads and executes .st source files
>    Fuel            Loads fuel files
>    config          Install and inspect Metacello Configurations from the 
> command line
>    save            Rename the image and changes file
>    test            A command line test runner
>    update          Load updates
>    printVersion    Print image version
>    eval            Directly evaluates passed in one line scripts
> 
> 
> $ ./vm.sh Pharo.image save --help
> 
> Usage: save <imageBaseName> [--delete-old]
>       <imageName>     a base name for the image
>       --delete-old    remove the old image and changes file
>       
> Documentation:
> Saves the image and changes file under a new name.
> 
> Examples:
>       # create a 'bar.image' and 'foo.changes'
>       $PHAROVM Foo.image saveAs bar
>       # create the same file as in the previous example but delete Foo.image 
> and Foo.changes
>       $PHAROVM Foo.image saveAs bar --delete-old
> ubuntu@ip-10-32-48-109:~/t3-push$ 
> 
> 
> And so on...
> 
> 
> --
> Sven Van Caekenberghe
> http://stfx.eu
> Smalltalk is the Red Pill
> 
> 


Reply via email to