Re: warning: forced break was overridden by some other event, should you be using bar checks?

[Kenneth Wolcott]

Thanks for the update, Jean!

On Tue, May 24, 2022 at 3:59 PM Jean Abou Samra <jean@abou-samra.fr> wrote:
>
> Le 13/01/2022 à 00:00, Jean Abou Samra a écrit :
> > There is no position information in the diagnostic
> > just because it is a bit inconvenient to do internally,
> > as there can be a number of reasons why a break
> > is disabled, and the information will come from different
> > sources depending on the cause. It might be possible,
> > though. My own take, however, would be to make \break
> > override all kinds of restrictions altogether and
> > just do what the user requested explicitly.
>
>
>
> Four months later ...
>
> For your information, this change has just landed in the
> LilyPond repository. It will appear in the next stable release
> (2.23.10). Now, if you use \break, LilyPond will just obey.
> This spares writing \bar "" if you really want a break in the
> middle of a measure. Of course, if it's unintendedly in the middle
> of a measure, the output will look silly, but it should be easier to
> find where the mistake occurred in the code thanks to point-and-click
> (bar checks obviously help a lot too). Another advantage is
> that \break will just bypass beams and other such unbreakable spanners
> without requiring extra overrides.
>
> Best,
> Jean
>
>