Does not yet cover the case Martin was looking for - omitting the second
accidental in a situation of a line-break on a tied accidental.
Can be done however by an explicit \omit, which should be only \once, because
otherwise it would omit accidentals from that point onwards.
The correct rendering (also showing the subsequent re-occurrence in the next
bar) is done by this snippet:
%%%
\relative c' {
c4 c c cis ~ |
\break
cis \once \omit Accidental cis cis d | cis cis cis d
}
%%%
The disadvantage of it is that this can only be used with an explicit line
break, as it will also be omitted if there is no linebreak on the tied note.
> On 3 Mar 2024, at 18:47, Damian leGassick <damianlegass...@mac.com> wrote:
>
> I had this yesterday, wasn’t immediately obvious but
>
> https://lilypond.org/doc/v2.25/Documentation/notation/accidentals
>
> hth
>
> Damian
>
>> On 3 Mar 2024, at 17:39, Martin Tarenskeen <m.tarensk...@kpnmail.nl> wrote:
>>
>>
>>
>>
>> Op zondag 3 maart 2024 om 18:33:26 +01:00:00 schreef Hans Aikema
>> <hans.aik...@aikebah.net>:
>>>
>>>
>>>
>>>> On 3 Mar 2024, at 17:26, Martin Tarenskeen <m.tarensk...@kpnmail.nl> wrote:
>>>>
>>>>
>>>> Hi LilyPonders,
>>>>
>>>> I bumped into a situation similar to this tiny example (In the real score
>>>> the linebreak happened at such a situation without a forced \break but the
>>>> result was the same):
>>>>
>>>> \relative c' {
>>>> c4 c c cis ~ |
>>>> \break
>>>> cis cis cis d |
>>>> }
>>>>
>>>> the sharp sign in the 2nd bar is printed twice. I am not sure if that's
>>>> the correct behaviour?
>>>> Without a \break the sharp is not printed for the tied 1st cis in the 2nd
>>>> bar, and only repeated for the 2nd cis in the 2nd bar.
>>>> I can imagine the reason to print the sharp sign after a linebreak and/or
>>>> pagebreak. But in such a case I would not repeat the sharp on the snd
>>>> quarter.
>>>
>>> The proposed behavior by Elain Gould in Behind bars (p 80) is to have a
>>> single sharp, without braces, on the second line before the tied note.
>>>>
>>
>> Yes, that's what I had in mind. How can I prevent LilyPond from printing a
>> second sharp in the second bar?
>>
>> MT
