Malte Meyn <lilyp...@maltemeyn.de> writes:
> Am 14.09.2017 um 11:14 schrieb Gianmaria Lari:
>> c4 c c d
>> (c4) c c c
>
> […]
>
>> c4 c c d
>> \mark "X" (c4) c c c
>
> The start of slur belongs to the d, not the c.
>
> Writing
> d (c)
> is possible and equivalent to
> d( c)
> but the latter more clearly says what’s going on.
>
> You tried to write
> d \mark X (c)
> so the \mark X goes between the d and the (. This cannot work, it has to be
> d( \mark X c)
> I would strongly recommend to put slur, beam, tie, … starts directly
> after the note they belong to instead of directly in front of the next
> note to avoid these situations.
Incidentally, current master delivers the following verbiage:
GNU LilyPond 2.21.0
Processing `sll.ly'
Parsing...
sll.ly:4:13: warning: Adding <> for attaching loose post-event
\mark "X"
(c4) c c c
Interpreting music...
sll.ly:4:16: warning: cannot end slur
\mark "X" (c4
) c c c
sll.ly:4:13: warning: unterminated slur
\mark "X"
(c4) c c c
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `/tmp/lilypond-U2WM3z'...
Converting to `sll.pdf'...
Deleting `/tmp/lilypond-U2WM3z'...
Success: compilation successfully completed
Is that more helpful than previously?
GNU LilyPond 2.19.80
Processing `sll.ly'
Parsing...
sll.ly:4:13: error: syntax error, unexpected EVENT_IDENTIFIER
\mark "X"
(c4) c c c
sll.ly:2:1: error: errors found, ignoring music expression
\fixed c' {
fatal error: failed files: "sll.ly"
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
