Re: Lily producing bad latex

[Han-Wen Nienhuys]

address@hidden writes:
 
> I may have misreported the problem, but the actual problem I was
> trying to point out was that when ly2dvi fails with a file like that,
> i.e. one where the lilypond parses ok, but TeX or LaTeX can't read the
> file, there's no pointer back to the actual line in the lilypond file
> that causes the failure.

Well actually, if you use point-and-click, you will get that
information in the form of src:  specials.

I think the best we could do is run some rudimentary syntax checks on
user strings that are dumped into output files. That's not a
particularly elegant solution, though.

> There is an even worse problem when running lilypond-book with the
> \lilypondfile statement, in that the error reporting doesn't even
> point you to the *name* of the file you need to look at.

Actually, it does: it will point to the lily-XXXX.tex file. The
corresponding lily-XXXX.ly file will direct you to the original file.

-- 

Han-Wen Nienhuys   |   address@hidden    | http://www.cs.uu.nl/~hanwen/