#103 specify extra TCL script on cmdline

[Manuel Bilderbeek]

Previously the autocommands in a settings.xml file could
be used to execute commands for a certain run (e.g. in
a WIndows shortcut). But now, the commands need to
be in init.tcl and there is no way to override the default
init.tcl on the cmdline, meaning there is no way to have
different autocommands for different shortcuts.
Iow: please add a way to specify an alternative init.tcl
file that should be sourced at startup to replace the old
autocommands properly.

[Maarten ter Huurne]

Logged In: YES
user_id=358343

I think this would be very useful with a small change: if
a script is specified on the command line, execute it
after init.tcl (not instead of). That way, init.tcl can
set the defaults and the specified script can override
only those settings which should have non-default values.

[Manuel Bilderbeek]

Logged In: YES
user_id=78178

OK, I agree. Changed the title to reflect this.

[Wouter Vermaelen]

Logged In: YES
user_id=356949

Implemented
-script <script.tcl>
command line option.

Can be used multiple times to source multiple scripts. The
scripts are executed (in order) after init.tcl.