Re: Slurs do not work with Larsen articulations

[David Kastrup]

Thomas Morley <address@hidden> writes:

> 2018-04-25 23:23 GMT+02:00 Carl Sorensen <address@hidden>:
>>
>>
>> On 4/25/18, 2:34 PM, "David Kastrup" <address@hidden> wrote:
>>
>>     So I see it more as a documentation challenge than a design failure.
>>
>>
>> I agree, and I think we can improve the documentation.
>>
>
> startSlur, stopSlur was by no means meant as a proposal!
> I was simply musing around.

Well, we have commands like that as well.  The single-character versions
are more intended as shortcuts.  That being said, I see in
ly/declarations-init.ly

%
% Code articulation definitions
%
noBeam = #(make-music 'BeamForbidEvent)
"|" = #(make-music 'BarCheck)
"[" = #(make-span-event 'BeamEvent START)
"]" = #(make-span-event 'BeamEvent STOP)
"~" = #(make-music 'TieEvent)
"(" =  #(make-span-event 'SlurEvent START)
")" = #(make-span-event 'SlurEvent STOP)
"\\!" = #(make-span-event 'CrescendoEvent STOP)
"\\(" = #(make-span-event 'PhrasingSlurEvent START)
"\\)" = #(make-span-event 'PhrasingSlurEvent STOP)
"\\>" = #(make-span-event 'DecrescendoEvent START)
"\\<" = #(make-span-event 'CrescendoEvent START)
"\\[" = #(make-span-event 'LigatureEvent START)
"\\]" = #(make-span-event 'LigatureEvent STOP)
"\\~" = #(make-music 'PesOrFlexaEvent)
"\\\\" = #(make-music 'VoiceSeparator)

so it does appear like there are no actual "longcuts" for those
commands.  I don't see a problem with that (keeps the stuff we want to
document in check) but would not know how others feel about the
alternative-lessness of those constructs.  For articulation shortcuts,
we do have long versions.

-- 
David Kastrup