Re: Orchestral score, can't find error

[Thomas Morley]

2012/10/7 Jay Hamilton <address@hidden>:

> I can see where some brackets are missing but it seems now that you point
> them out that the log/error file and Frescobaldi should have been able to
> point them out too.  And neither did.

Not sure what you want to say.
Compiling your code after deleting a _needed_ bracket the terminal shows:

GNU LilyPond 2.16.0
Processing `atest-15.ly'
Parsing...
atest-15.ly:1826:0: error: syntax error, unexpected >>

>>
atest-15.ly:1891:0: error: syntax error, unexpected >>

>>
/home/<name>/lilypond/usr/share/lilypond/current/ly/init.ly:111:66:
error: syntax error, unexpected $end
   (ly:parser-error parser (_ "expected error, but none found"))))

fatal error: failed files: "atest-15.ly"

This is the common terminal-output for a missing bracket.
Frescobaldi returns similiar, adding (in german)

LilyPond [atest-15.ly] wurde mit dem Return-Code 1 beendet.

Do you expect that you get a hint which type of bracket is missing at
which line of your code?
I can't imagine that LilyPond will be ever that smart. More, I think
it's impossible.


Cheers,
  Harm