From: Beni C. <cb...@te...> - 2002-12-11 09:22:01
|
[New to the list, rST rocks :] On 2002-12-10, David Ascher wrote: > Is there an option I don't know about to let docutils barrel through and never > raise an exception when processing a document?I'm all for strictness in > formatting in 99% of cases, but I'd like to use docutils to convert old > documents written in "vague structured text" into HTML, in cases where there > is no reason to go back to the original texts to make them conform. > I don't think that skipping errors is the right approach since it can guess wrongly what you meant. DWIMs are known to make people sorry for using them :-). However the cycle of running docutils and fixing the source is not very convenient when you are in a hurry. TeX's approach of stopping and suggesting interactive fix possibilities could be more effecient (if the messages are less criptic ;-) but doesn't save the corrections in any way. So how about a ``--halt=edit`` mode that will spawn your text editor on the line where the first error happened and after you exit the editor, it will restart from the beginning (or maybe continue if the input file's timestamp hasn't changed)? -- Beni Cherniavsky <cb...@tx...> What's lower level than machine code? A spreadsheet: not only addresses are numeric and hand-allocated but also all loops are hand-unrolled and all calls hand-inlined... (and macros are unheard of, of course). |