On Thu, Sep 18, 2014 at 9:40 PM, Joerg Jaspert <jo...@debian.org> wrote:
>> Looks like failure is the sanest option. > 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. Besides, stopping meanwhile updating the generated files isn't good either, as the end user has then not many clues of what was wrong. And users do _not_ read log files. It's very sad, but it's a fact :-). So, I guess for static stuff I could change the default to the good old VB "On Error Resume Next". 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. 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. 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. -- Steve Schnepp http://blog.pwkf.org/tag/munin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
