An update on my investigations...
> pymol-2.1.0+dfsg/examples/cookbook/scenes2movie.pml
>
> Running that script by hand shows why -- it's playing the movie in a loop
> forever. Does someone know pymol well enough to say that the "mplay" syntax
> has changed or how to limit the movie to just one run through?
With pymol 1.8, "pymol -c foo.pml" exits immediately after the mplay command
at the end of the script ("-c" means run in batch mode). With pymol 2.1, the
script does not exit after an mplay and instead loops forever.
Adding an explicit "quit" or "mstop" to the end of pml script solves this
particular failure. I suspect there are more beyond this one to fix and will
investigate further.
> > Output to stderr normally causes a test to fail. One can overrule that
> > by add allow-stderr to the test Restrictions if the output is expected
> > and to be ignored.
>
> The stderr output also indicates that the test runner think that the test
> run has failed. Once more with set -x in place, the runner is not finding
> 'PyMOL: normal program termination.' in the pymol output.
That part I am yet to investigate... this sort of shell script debugging
reminds me of the normal level of complexity for a shell script where I wish
it was in some other language.
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
