On 13703 March 1977, Steve Schnepp wrote: >> I don't think it's sanest. It's easiest, yes. But the failure here is > Holger, you might have misread the bug. To me, ignoring the faulty > file for static stuff seems a sane default indeed.
Yep. Maybe output a log message about not updating it due to $whatever, but don't stop the whole run. > And for the templates stuff, I think any error could be written in the > output file, in a big fat red font. But in the expected place, so the > user has a change to see it. Ay, though that one has less chance of getting bad the way i described. Most errors in templates are pretty visible to users :) > That said, the way it works currently has also its adepts. Mostly > because a silent failure is sometimes better than a loudly one. > Specially for tech-sawy users, or for transient ones. I'm not sure it has any advantage to fail in this case, ... > The last behavior should then be optional. The default is still to be > decided, but I usually favor ease-of-use for a newbie, so the red > warning has my personal preference. ... but having it configurable, no matter which way is default, is certainly fine. -- bye, Joerg <Sahneschnitter> Aquariophile: welches debian/ welche xfree version? <Aquariophile> woody <Aquariophile> Xfree version 86 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
