lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 5272: Add \depart <markup> (issue 337520043 by address@hidden)


From: Dan Eble
Subject: Re: Issue 5272: Add \depart <markup> (issue 337520043 by address@hidden)
Date: Tue, 6 Feb 2018 22:59:56 -0500

On Feb 6, 2018, at 21:12, Simon Albrecht <address@hidden> wrote:
> 
> Brainstorming (NB, only brainstorming) on the name:
> 
> Normal rehearsal marks refer to the beginning of a section, while these refer 
> to the end of a section, so an input command might be \endMark "D.S.". You 
> still have to complete it to ‘end-of-section mark’ in your head, but \depart 
> seems far too unspecific to me.

Maybe.  We would have to decide whether \mark is a verb or a noun.  If it’s a 
verb, the command could be \markEnd.

\end... might create some mental tension given that there are \stop… commands 
for spans.

In my mind, it would be appropriate to use this feature for an instruction such 
as “optional cut to m. 66,” which I would associate more closely with the 
beginning of the section to be cut rather than the end of the preceding section.


> Other idea: \goTo. Maybe provide a syntactic-sugar-y \Fine (or \fine) command 
> to avoid the weirdness of \goTo "Fine”?

\goTo was obvious to me, too, and I would be happy with it, but I was concerned 
that my level of comfort comes mostly from being a software developer.

On the other hand, \goTo seems unlikely to resemble whatever we settle on for 
the grob name… unless everyone likes GoToScript.


> Naming the grob is also tricky. I’m pretty sure that there has never been a 
> technical term for this kind of instructions…
> AfterSectionScript? (meh…) SectionScript? AfterSectionMark?

Gould uses the words “point of departure” (p. 239).  If she had meant it as 
jargon, she would have put it in her index, but I latched onto it anyway.
— 
Dan




reply via email to

[Prev in Thread] Current Thread [Next in Thread]