View Single Post
Old 02-19-2013, 07:28 AM   #4
exaltedwombat
Evangelist
exaltedwombat ought to be getting tired of karma fortunes by now.exaltedwombat ought to be getting tired of karma fortunes by now.exaltedwombat ought to be getting tired of karma fortunes by now.exaltedwombat ought to be getting tired of karma fortunes by now.exaltedwombat ought to be getting tired of karma fortunes by now.exaltedwombat ought to be getting tired of karma fortunes by now.exaltedwombat ought to be getting tired of karma fortunes by now.exaltedwombat ought to be getting tired of karma fortunes by now.exaltedwombat ought to be getting tired of karma fortunes by now.exaltedwombat ought to be getting tired of karma fortunes by now.exaltedwombat ought to be getting tired of karma fortunes by now.
 
Posts: 438
Karma: 1703930
Join Date: Nov 2011
Device: none
I've been thinking this through.

Pretty Print is good to have. Generally we want it turned on. Agreed?

It's very useful to be able to save bad code "as-is" and come back to it later. But it's only an occasional requirement.

Many of us have developed a Ctrl-S reflex while working in Sigil, or any other program. When the phone rings, nature calls or just because a few minutes have passed since we last did it - save the file!

This sensible and universally-recommended action has become dangerous. Before, if there was bad code it just wouldn't save. Now it WILL, but it changes the code.

Suggestion. Bring back the old warning when Save of malformed code is attempted. (It's still there, when switching from Code to Page view.) But add one further option. Alongside "Fix manually" and "Fix automatically" put "Save as-is. Pretty Print and HTML Tidy will be disabled. Switch them back on if required."

Last edited by exaltedwombat; 02-19-2013 at 07:31 AM.
exaltedwombat is offline   Reply With Quote