Re: How to read a error message?

[David Kastrup]

Urs Liska <address@hidden> writes:

> Am 14.03.2017 um 10:43 schrieb David Kastrup:
>> Urs Liska <address@hidden> writes:
>>
>>> Am 14.03.2017 um 09:00 schrieb David Kastrup:
>>>> and then the offending line, split into two just at the offending
>>>> location.  In your case, the first occurences of h are flagged since h
>>>> is not part of the default note language.
>>> To add something more general to that: The "error: unrecognized string"
>>> indicates that LilyPond is given something to parse (here: "h") which it
>>> doesn't understand ("recognize") at this place. It can be a note name in
>>> the wrong language but it could also be a misspelled command (e.g.
>>> \brake instead of \break) or a variable you have declared in another
>>> file which you forgot to include.
>>>
>>> So essentially this error tells you "There is *something* wrong with
>>> your input but I can't tell you what exactly". And LilyPond can't tell
>>> you "this is not a note name" here because there are plenty of other
>>> valid things that could go there, articulations, dynamics, ties,
>>> arbitrary commands or Scheme expressions ...
>> None of which have the form of a string.  I do think that the error
>> message is too circumlocutory.
>>
>
> Maybe something like Python3:
>
>>>> prnit("Something")
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> NameError: name 'prnit' is not defined
>
> We could have something like:
>
> error: unknown item 'h'
>
> in the OP's example?

Just running "make test" on a proposal of mine: discussion will then be
best done on the Rietveld issue.

-- 
David Kastrup