[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
melismaBusyProperties: scheme syntax vs. lily syntax
From: |
Simon Albrecht |
Subject: |
melismaBusyProperties: scheme syntax vs. lily syntax |
Date: |
Sun, 15 Jul 2018 23:01:27 +0200 |
Hello everybody,
I just noticed that it’s possible to use the LilyPond symbol list/key
list syntax when setting melismaBusyProperties. However, the doc string
reads
"A list of properties (symbols) to determine whether a melisma is playing.
Setting this property will influence how lyrics are aligned to notes.
For example, if set to @code{'(melismaBusy beamMelismaBusy)},
only manual melismata and manual beams are considered.
Possible values include @code{melismaBusy}, @code{slurMelismaBusy},
@code{tieMelismaBusy}, and @code{beamMelismaBusy}."
Would we want to change the first code example to
@code{melismaBusy,beamMelismaBusy}
or otherwise suggest the new syntax?
Best, Simon
- melismaBusyProperties: scheme syntax vs. lily syntax,
Simon Albrecht <=
- Re: melismaBusyProperties: scheme syntax vs. lily syntax, David Kastrup, 2018/07/15
- Re: melismaBusyProperties: scheme syntax vs. lily syntax, Carl Sorensen, 2018/07/15
- Re: melismaBusyProperties: scheme syntax vs. lily syntax, Simon Albrecht, 2018/07/15
- Re: melismaBusyProperties: scheme syntax vs. lily syntax, Carl Sorensen, 2018/07/15
- Re: melismaBusyProperties: scheme syntax vs. lily syntax, Thomas Morley, 2018/07/16
- Re: melismaBusyProperties: scheme syntax vs. lily syntax, David Kastrup, 2018/07/16
- Re: melismaBusyProperties: scheme syntax vs. lily syntax, Thomas Morley, 2018/07/16
- Re: melismaBusyProperties: scheme syntax vs. lily syntax, David Kastrup, 2018/07/16