I think most developers are used to having a full error log - which is definitely the right default behaviour for lilypond. On the other hand I can fully understand that especially for users that aren't used to software development a full error log can be quite a mess to the (untrained) eye.
In this context I could imagine a paramater that kind of highlights the first few error messages (or only shows the first N error messages) being very forthcoming to some people without a dev background. Or maybe at the end of the compilation output a clearly marked: "First (few?) Error(s): ...."
~Christian
Le 29/03/2022 à 08:46, Martín Rincón Botero a écrit :
> +1. I think making it customizable (with a --cascade-level parameter)
> wouldn't add much value considering developing effort, though.
> Lilypond, like Python f. ex., should simply report the first error
> (and ideally immediately abort compilation).
I strongly disagree :-)
When there is an error, the default should be to continue as long as
possible. For large projects where the compilation takes time, you want
to have some viewable output even if there is a glitch somewhere. I also
think you are overestimating the "developing effort" -- such an option
would be absolutely trivial to add. I am not sure it is worth it though.
As David said, hiding errors is always a heuristic process. I think this
would be better addressed by a convenient "jump to first error" button
in Frescobaldi.
Jean