But isn't the start time of this <> the start time of the c4 in the second line, so that <>( c4) is equivalent to c4(); which causes the warnings 'cannot end slur' for ')' and 'unterminated slur' for '('? My guess is that this insertion of <> makes things more complicated for us, unenlightened users, if anything.

My preference would be to clearly explain that '(' is an attribute of the note that directly precedes it.

Rutger

On 14-09-17 11:53, Malte Meyn wrote:


Am 14.09.2017 um 11:43 schrieb David Kastrup:
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?

If adding <> is the thing that is done now, of course this is more helpful. Would it be possible to add that <> in the following warnings too? I suppose no because locations in the file would get messed up if added things were shown.

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to