Urs Liska writes:
> Am 11.01.2013 23:25, schrieb David Kastrup:
>> David Kastrup writes:
>>
>>> Noeck writes:
>>>
Hi,
why does compiling this code fail to compile with lilypond?
\version "2.16.0"
{ a }
%
>>> No, the problem is that there _is_ no last line
Am 11.01.2013 23:25, schrieb David Kastrup:
David Kastrup writes:
Noeck writes:
Hi,
why does compiling this code fail to compile with lilypond?
\version "2.16.0"
{ a }
%
The empty comment in the last line is the problem.
No, the problem is that there _is_ no last line. You have an EOF
David Kastrup writes:
> Noeck writes:
>
>> Hi,
>>
>> why does compiling this code fail to compile with lilypond?
>>
>> \version "2.16.0"
>> { a }
>> %
>>
>> The empty comment in the last line is the problem.
>
> No, the problem is that there _is_ no last line. You have an EOF in the
> middle of
>> The empty comment in the last line is the problem.
>
> No, the problem is that there _is_ no last line. You have an EOF in the
> middle of the line (not every editor will even allow producing that).
I see. I would not consider it as a critical bug. I was just curious.
It would make sense, if
Noeck writes:
> Hi,
>
> why does compiling this code fail to compile with lilypond?
>
> \version "2.16.0"
> { a }
> %
>
> The empty comment in the last line is the problem.
No, the problem is that there _is_ no last line. You have an EOF in the
middle of the line (not every editor will even all
Hi,
why does compiling this code fail to compile with lilypond?
\version "2.16.0"
{ a }
%
The empty comment in the last line is the problem. But I do not
understand why. Removing the % works obviously. Writing some text after
the % works, too. But an empty comment fails. Or is that expected for
