Quote:
Originally Posted by mrmikel
I don't think pretty print has ever caused me trouble, on reflection. The automatic repairs is when you try to save and it tells you it is malformed and offers to fix it for you. I don't think I would ever take it up on the offer unless I had just saved it and then saved the automatically fixed version with a different file name.
You can make a note of what line you are on just before you switch views or save, since it will tell you that the paragraph is not closed on line 4000 at the end of the html, when the error is nearly always just where you were working. It will also give you the same sort of message with unclosed anchors in the middle of the paragraph so it can be baffling.
|
Hey mrmikel. I hear you about the pretty print's automatic saving feature, but the thing is when you get that warning (saying,'fix it either manually or automatically') and you go to save it, it won't let you without either manually or automatically fixing the error,and if you don't know how to fix it manually, what do you do? So I agree it's wise to save the old version and then see what the automatic fixing does, but how do you do that given it won't let you without fixing it?
And a second question: Is pretty print's automatically fixing an error that problematic really? I mean, it tells you what the error is, where it is. And if you can't figure it out, it seems pretty print's fixing it would be a low risk thing to do. Do you have experience with getting really bad results using the automatic fixing?
Thanks.