FWIW, I do think terminating the list is the right thing to do for non-existent plugins, plugins that report failures, and Tools that report failure. Continuing would be dangerous and the log file will show you exactly what went wrong so you can fix the Automate list, then revert to the last save Checkpoint or reload the file and run the corrected list.
Quote:
Originally Posted by RbnJrg
Not an error, but in order to see how Sigil can process an erroneous command, I opened automate01.txt and I included by hand the name of the plugin "XX_Everything" (of course, the plugin is imaginary, doesn't exist). Well, I received the following message:
Code:
StandardizeEpub running
Restructure completed.
StandardizeEpub skipped since not an epub3 <<
RemoveInLineStyles running
ReformatCSSMultipleLines running
ReformatCSSMultipleLines skipped since not an epub3 <<
XX_Everything running
Missing or unknown plugin or tool: XX_Everything
Automation List Failed << Sigil doesn't process the commands that follow
Maybe it could be preferable that Sigil -when there is an error- instead of aborting the list, it will be able to offers the users the option to continue or to abort. |