Re: How to read a error message?

[Urs Liska]

Am 14.03.2017 um 11:02 schrieb David Kastrup:
> Urs Liska  writes:
>
>> Am 14.03.2017 um 10:43 schrieb David Kastrup:
>>> Urs Liska  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 "", line 1, in 
>> 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.
>

OK

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Re: How to read a error message?

[David Kastrup]

Urs Liska  writes:

> Am 14.03.2017 um 10:43 schrieb David Kastrup:
>> Urs Liska  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 "", line 1, in 
> 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

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

Re: How to read a error message?

[Urs Liska]

Am 14.03.2017 um 10:43 schrieb David Kastrup:
> Urs Liska  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 "", line 1, in 
NameError: name 'prnit' is not defined

We could have something like:

error: unknown item 'h'

in the OP's example?

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Re: How to read a error message?

[David Kastrup]

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

-- 
David Kastrup

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

Re: How to read a error message?

[Urs Liska]

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

HTH
Urs

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Re: How to read a error message?

[Scoutladen - Ralph Fröhlich]

Thank you very much. This will help me.


Am 14.03.2017 um 09:00 schrieb David Kastrup:

Scoutladen - Ralph Fröhlich  writes:


Hi,

hope to find some informations here about reading error messages

Example:

Processing `.../file.ly'
Parsing...
.../file.ly:16:30: error: unrecognized string, not in text script or \lyricmode
   fis8 fis fis fis d d d4 g (
  h) h h8 h8
.../file.ly:16:33: error: unrecognized string, not in text script or \lyricmode
   fis8 fis fis fis d d d4 g (h)
 h h8 h8

Where can I find a short description?

It's just filename:linenumber:columnnumber: errormessage

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.

Maybe this particular error message should be "`h' is not a notename"
instead.  It's nice that the string would be allowed in a text script or
\lyricmode, but if someone writes

blabla = \new Lyrics { Shall I com- pare thee to a summer's day? }

the error message "`Shall' is not a note name" is probably clue enough
about what is happening.

Namely we should say what is wrong _here_ rather than mentioning where
it could be right.



--
Abonniere unseren Kanal bei Youtube http://www.youtube.de/jurtenland

Besuche uns bei Facebook http://www.facebook.com/zeltemitfeuerimherzen
Folge uns bei Twitter: http://www.twitter.com/jurtenland
_
Jurtenland - Zelte mit Feuer im Herzen!
Troyerladen - Zieht euch warm an!
Kistenladen - Verpacken, transportieren, lagern!
_

Scoutladen
Ralph Fröhlich
Weingartenstr. 35
77654 Offenburg

Tel. 0781 9483517
Fax. 0781 9483518

ra...@scoutladen.de
http://www.scoutladen.de
http://www.jurtenland.de
http://www.troyerladen.de
http://www.kistenladen.de

UstId: DE238956415
_
Textildruck | Ausrüstung | Bekleidung | und mehr...


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

Re: How to read a error message?

[David Kastrup]

Scoutladen - Ralph Fröhlich  writes:

> Hi,
>
> hope to find some informations here about reading error messages
>
> Example:
>
> Processing `.../file.ly'
> Parsing...
> .../file.ly:16:30: error: unrecognized string, not in text script or 
> \lyricmode
>   fis8 fis fis fis d d d4 g (
>  h) h h8 h8
> .../file.ly:16:33: error: unrecognized string, not in text script or 
> \lyricmode
>   fis8 fis fis fis d d d4 g (h)
> h h8 h8
>
> Where can I find a short description?

It's just filename:linenumber:columnnumber: errormessage

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.

Maybe this particular error message should be "`h' is not a notename"
instead.  It's nice that the string would be allowed in a text script or
\lyricmode, but if someone writes

blabla = \new Lyrics { Shall I com- pare thee to a summer's day? }

the error message "`Shall' is not a note name" is probably clue enough
about what is happening.

Namely we should say what is wrong _here_ rather than mentioning where
it could be right.

-- 
David Kastrup

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

Re: How to read a error message?

[Scoutladen - Ralph Fröhlich]

Ok... so far so good... thank you for the tipp. That works fine.



Am 14.03.2017 um 08:54 schrieb Marc Hohl:

Am 14.03.2017 um 08:49 schrieb Scoutladen - Ralph Fröhlich:

Hi,

hope to find some informations here about reading error messages

Example:

Processing `.../file.ly'
Parsing...
.../file.ly:16:30: error: unrecognized string, not in text script or
\lyricmode
  fis8 fis fis fis d d d4 g (
 h) h h8 h8
.../file.ly:16:33: error: unrecognized string, not in text script or
\lyricmode
  fis8 fis fis fis d d d4 g (h)
h h8 h8

Where can I find a short description?


I cannot answer this in general, but this looks like using german note 
names without declaring it first.


Do you have

\language "deutsch"

stated in your input file?

HTH,

Marc



Best regards
Ralph





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


--
Abonniere unseren Kanal bei Youtube http://www.youtube.de/jurtenland

Besuche uns bei Facebook http://www.facebook.com/zeltemitfeuerimherzen
Folge uns bei Twitter: http://www.twitter.com/jurtenland
_
Jurtenland - Zelte mit Feuer im Herzen!
Troyerladen - Zieht euch warm an!
Kistenladen - Verpacken, transportieren, lagern!
_

Scoutladen
Ralph Fröhlich
Weingartenstr. 35
77654 Offenburg

Tel. 0781 9483517
Fax. 0781 9483518

ra...@scoutladen.de
http://www.scoutladen.de
http://www.jurtenland.de
http://www.troyerladen.de
http://www.kistenladen.de

UstId: DE238956415
_
Textildruck | Ausrüstung | Bekleidung | und mehr...


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

Re: How to read a error message?

[Marc Hohl]

Am 14.03.2017 um 08:49 schrieb Scoutladen - Ralph Fröhlich:

Hi,

hope to find some informations here about reading error messages

Example:

Processing `.../file.ly'
Parsing...
.../file.ly:16:30: error: unrecognized string, not in text script or
\lyricmode
  fis8 fis fis fis d d d4 g (
 h) h h8 h8
.../file.ly:16:33: error: unrecognized string, not in text script or
\lyricmode
  fis8 fis fis fis d d d4 g (h)
h h8 h8

Where can I find a short description?


I cannot answer this in general, but this looks like using german note 
names without declaring it first.


Do you have

\language "deutsch"

stated in your input file?

HTH,

Marc



Best regards
Ralph





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