Comment #7 on issue 1356 by d...@gnu.org: LilyPond-style comments embedded
in a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356#c7
Record $ and # expressions inside of #{ #} for better correlation
This improves and robustifies the closure handling of #{ ... #} and
makes for proper error messages (well, the column display for the
first line of #{ ... environments is missing the start of the line up
to #{, but file and line number are ok). When the user managed to
confuse Lilypond sufficiently that it has managed to preparse $ and #
closures not actually in the source, Lilypond just reverts to
interpreting the contents straight.
This should fix issue 1356 to the degree where only extremely ugly
input will cause problems.
http://codereview.appspot.com/5437055
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
