Hi,
Nice! 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? Maybe, yes.
I have some other work high on my priority list (there's a certain
larger pending merge request...), but I could at least to a regression
test run and see what such a change would effect globally.
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.
Lukas
