Re: \mark and slur

[David Kastrup]

Malte Meyn <address@hidden> writes:

> 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.

I'm not sure it would help here.  People tend to ignore warnings
anyway.  The idea was to suggest a course that would help in case that
the result is indeed what people wanted.

> 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.

Locations in the file are locations in the file.  LilyPond does not
change the input.  Creating location markers for imaginary input seems
like a really bad idea.

-- 
David Kastrup