> In the following example, when a note has a slur and a tie and
> hide-tied-accidental-after-break is enabled, the slur is incorrectly
> placed when another staff has many accidentals.
Thanks for the report. However, I don't think the problem is
especially related to accidentals; it's rather one of the many cases
where LilyPond's automatic tie and slur positioning algorithm makes
bad choices – there are plenty of issues already registered in our bug
tracker, some of them older than 15 years and still unresolved, alas.
Just look up the labels 'ties' and 'slurs'.
Note that you get almost the same bad results in your example if you
omit 'hide-tied-accidental-after-break'. Similarly, the results are
differently bad if you omit the accidentals altogether.
```
\version "2.25.13"
<<
\new Staff {
\override Tie.color = #red
\override Accidental.hide-tied-accidental-after-break = ##t
cis''1~( \break 1)
}
\new Staff {
R1 1
}
>>
<<
\new Staff {
\override Tie.color = #red
cis''1~( \break 1)
}
\new Staff {
R1 1
}
>>
<<
\new Staff {
\override Tie.color = #red
c''1~( \break 1)
}
\new Staff {
R1 1
}
>>
```
Werner
