It seems like a good idea to me. There often isn't a good reason to have a good compile with barcheck failures.
Knute Snortum (via Gmail) On Thu, Dec 3, 2015 at 3:13 PM, Urs Liska <u...@openlilylib.org> wrote: > Hi, > > there was the request for a way to have barcheck failures cause errors > instead of warnings: > http://lists.gnu.org/archive/html/lilypond-user/2015-12/msg00074.html > > I think this is a valid use case as very often you don't actually want > to have the compiled score when it contains barcheck failures, erroring > out with a useful message pointing to the input location can be a > time-saver. > > This could be controlled by a command line option (e.g. > -derror-on-barcheck). > > Before giving it a try and preparing a patch I would like to get some > feedback if this idea seems good. > > Best > Urs > > _______________________________________________ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond > _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
