>> I think we should provide a proper callback function within
>> LilyPond to fix this.
>
> Do you mean an override like mine should become the default?
Yes.
>> What exactly is your reason to handle `|` differently?
>
> The reason is that I liked the reduced distance between hairpin and
> barline in the '|' case:
>
> I thought this looked better than the version with global (LEFT
> . LEFT) setting:
>
> But the difference is admittedly tiny, and maybe I was wrong in the
> first place.
>
> It probably played a role that the situation "hairpin stopping at |
> barline" is very common and well-tested in LilyPond, so I deemed it
> improbable that a carefree change of it made by me should be an
> improvement in that case.
Well, to me it's kind of unnatural to compute the distance between a
hairpin and an adjacent bar line using the *right* edge of the bar
line. Using the left one makes more sense, I believe. So I vote for
changing this for all types of bar lines.
Werner
