use "smt" (rather than "metis") to reconstruct SMT proofs

don't pass too many facts on the first iteration of the SMT solver

catch TimeOut exception

ensure the SMT solver respects the timeout -- Mirabelle revealed cases where "smt_filter" apparently never returns

if SMT used as a filter in a loop fails at each iteration, returns the first error, not the last, since it is more informative -- the first error typically says "out of memory", whereas the last might well be "the SMT problem is unprovable", which should be no surprise if too many facts were removed

removed explicit "Interrupt" handling for conformity with async model -- unfortunately the user loses the information about how many scopes were checked, but this needs to be retought with the new interface anyway

make Nitpick datatype tests faster to make timeout less likely

invoke SMT solver in a loop, with fewer and fewer facts, in case of error

always honor the max relevant constraint

more robust treatment of suppressed quotes concerning replacement text -- for improved copy/paste behaviour;

updated generated files;

tweaked pdf setup to allow modification of \pdfminorversion;

merged;

updated generated files;

basic setup for literal replacement text in PDF, to support copy/paste of Isabelle symbols;

updated generated file;

more literal appearance of antiqopen/antiqclose;

'example_proof' is treated as non-schematic statement with irrelevant proof (NB: even regular proofs can contain unreachable parts wrt. the graph of proof promises);

continue after failed commands;

added Keyword.is_heading (cf. Scala version); tuned;

updated keywords;

mark 'cd' and 'commit' as control command -- not usable in asynchronous document model, likely to cause confusion in Proof General;

somewhat more uniform timing markup in ML vs. Scala;

somewhat more uniform timing in ML vs. Scala;