Le 03/12/2022 à 18:00, Dan Eble a écrit :
It's the same concern as from the beginning: I was reluctant to allow assigning
multiple labels to the same moment in a performance because of known and
unknown complications.
For example, if a moment were marked with both 𝄌 and Part II, what should th
On Dec 3, 2022, at 08:48, Jean Abou Samra wrote:
>
> It rejects the \sectionLabel that comes at the same
> time as an implicit \codaMark.
>
> Should this be supported, or is there a reasoning that
> I am missing?
It's the same concern as from the beginning: I was reluctant to allow assigning
m
On Dec 3, 2022, at 10:25, Jean Abou Samra wrote:
>
> Le 03/12/2022 à 16:18, Dan Eble a écrit :
>> Printing "Coda" instead of a coda mark is the defining use case for
>> \sectionLabel.
>
> But judging from how \repeat segno uses it and from its break-visibility,
> \codaMark is for a jump to the
Le 03/12/2022 à 16:18, Dan Eble a écrit :
Printing "Coda" instead of a coda mark is the defining use case for
\sectionLabel.
But judging from how \repeat segno uses it and from its break-visibility,
\codaMark is for a jump to the coda, not for the start of the coda itself,
isn't it?
OpenP
On Dec 3, 2022, at 08:48, Jean Abou Samra wrote:
>
> It rejects the \sectionLabel that comes at the same
> time as an implicit \codaMark.
Printing "Coda" instead of a coda mark is the defining use case for
\sectionLabel. I'll try to take a closer look at the example soon.
—
Dan
I thought that with c7b238579b3d19c6ac2bc9e7160c803390f7bc07
as well as text marks, all meaningful cases of simultaneous
mark-like events were covered, but there is a question on
-user-fr about this case:
\version "2.25.0"
{
\repeat segno 2 {
\sectionLabel "Part I"
c'1
\break
\
