View Single Post
Old 02-20-2013, 06:53 AM   #23
exaltedwombat
Guru
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: 878
Karma: 2457540
Join Date: Nov 2011
Device: none
Quote:
Originally Posted by Hitch View Post
ExaltedWombat:

Weren't you one of the folks exhorting for this "save it in whatever bad state it's in" change in the first place, or am I misremembering?
Yes, and I stand by it. There are occasions - maybe rare ones - when being able to suspend a session "as is" will be useful.

The price seems to be giving up automatic Pretty Print (did anyone actually choose automatic HTML Tidy?). No great loss?

But users who have developed an efficient Ctrl-S reflex, and relied on Sigil's refusal to save malformed code as protection against PP messing things up, should be warned and educated. At present the manual recommends enabling auto-PP, and doesn't mention the new ability to save bad code.

All it needs is a warning - "with your current settings, proceeding with Save may change your code".

Last edited by exaltedwombat; 02-20-2013 at 06:59 AM.
exaltedwombat is offline   Reply With Quote