Re: Lilypond error behaviour

[Thomas Morley]

2016-04-19 22:41 GMT+02:00 Sharon Rosner <address@hidden>:
>> Now it appears that there are people who want to change that
>> because they want to add some sort of post-processing by machine
>> (embedding LP in Makefiles, or into a server), or even just the
>> imposition of some tidier design principle that has nothing
>> to do with printing music.
>
> Lilypond's handling of errors is fine. It's just the reporting of errors
> that's not.

Btw,
have a look into lily.scm
Near the end of
(define-public (lilypond-main files) ...
you'll find:
    (if (pair? failed)
        (begin (ly:error (_ "failed files: ~S") (string-join failed))
               (ly:exit 1 #f))
        (begin
          (ly:exit 0 #f)))))

comment (ly:error ...
And the otherwise all present "Fatal error ..." message will disappear.
Instead you'll get:
"warning: Compilation completed with warnings or errors"

"Compilation completed" doesn't say anything about success or the kind
of errors, though.

Ofcourse other consquences may happen, you'll have to try it out.

>
>> I think I'll risk making you uncomfortable in order to argue
>> against arbitrary non-generation (or deletion) of PDF output.
>> Sorry.
>
> Again, it's rather the exit code, not the presence or absence of PDF's.
>
> On a more general note, I think it's a real shame that whenever someone
> wants to build any kind of tooling around lilypond, some "people" here get
> into bunker mode. Lilypond is great, yes, but it could be improved, you
> know...

I'm also irritated. Why should there a contrast while LilyPond is used
by programmers/developers and non-programmers?

If LilyPond syntax is obfuscated by more and more cryptic things, only
understandable for experienced programmers, yes, then we have a
problem - this probably is the reason for concerns mentioned by some
participiants here.
I don't think this is the case up to now, more correct is the opposite, imho

> Andrew, if you're still reading this futile exchange,

It would be a little less futile, if people would try harder to read
and to understand what was written and think about it.
Really no reason for a flame-war.

> just turn on
> warning-as-error and be done with it.

As I wrote days ago ...

>
> Sharon


Cheers,
  Harm