OK, Nico. I get it. I had messed up the -c and -C flags. I've uploaded
corrections as part of 11.7.4_dev. MonsterScript checks rapidly.
Bob
On Sun, Oct 12, 2008 at 8:41 PM, Robert Hanson [EMAIL PROTECTED] wrote:
I think what has changed is that it is now opening the files remotely --
the
Thanks a lot !
I will check later on my computer, but that's what I was looking for :
otherwise MonsterScript was checking in about 20mn in my laptop + 20mn for
running it :)
Nico
On Mon, Oct 13, 2008 at 4:59 PM, Robert Hanson [EMAIL PROTECTED] wrote:
OK, Nico. I get it. I had messed up the -c
It's for the unit tests, where the script checking is done calling :
viewer.setAppletContext(, null, null, -n -C );
Is there a way to pass the noload argument there ?
Nico
On Sat, Oct 11, 2008 at 11:58 PM, Robert Hanson [EMAIL PROTECTED] wrote:
The -c flag checks scripts, but it also does all
It needs to open the files, otherwise the scripts can't be checked.
On Sun, Oct 12, 2008 at 3:15 AM, Nicolas Vervelle [EMAIL PROTECTED]wrote:
It's for the unit tests, where the script checking is done calling :
viewer.setAppletContext(, null, null, -n -C );
Is there a way to pass the noload
I think what has changed is that it is now opening the files remotely -- the
default directory is being set to
defaultdirectory=http://chemapps.stolaf.edu/jmol/docs/examples-11/data;
That's so that the files are found.
Bob
On Sun, Oct 12, 2008 at 8:39 PM, Robert Hanson [EMAIL PROTECTED]
The -c flag checks scripts, but it also does all the file opening, and that
will take time. To check a script without file loading, you need to create a
little script that contains:
script xxx.spt check noload
and then use
Jmol -s thatscript.spt
Bob
On Sat, Oct 11, 2008 at 4:44 PM, Robert
I don't think so. I'll check. I usually do the script running, not just
checking, so we'll see.
On Sat, Oct 11, 2008 at 4:22 PM, Nicolas Vervelle [EMAIL PROTECTED]wrote:
Hi,
Script checking seems very slow with the latest versions (as if it was not
only checking the script, but also running
