[Turtle91]

Soooo....I'm cleaning up a book with 145000 chapters/files. I make a change - a very simple one that shouldn't be any problem - and when I try and save Sigil pukes and says it can't save because there is some malformed code....somewhere.

I could let Sigil fix it automatically...but I would rather not....who knows what would happen then?? So I go file by file and open them one at a time looking for the red error box in the preview pane. Did I mention there are 145000 chapters??...takes FOREVER. I can't even run a report to see if that would help because of the malformed html.

I've lived with this for a couple years...I took it as my just deserts for making the mistake in the first place...but JUST THIS WEEK I found a way for Sigil to tell me which file actually has the error on it.

"How?" you ask. I select all the files in the text folder then right-click and attempt to link a stylesheet. It doesn't let me do this either, but the error code includes the name of the first file with an error!!

Hallelujah!!

Of course, it only lists one errant file at a time....so my request is: Can we formalize that functionality into an error listing? Something along the lines of the "Report" page but with a list of offending files that could be clicked on to open.

That would make my blundering so much more enjoyable.....


Thanks,