Updates:
Status: Fixed
Owner: [email protected]
Labels: Fixed_2_15_21
Comment #2 on issue 1416 by [email protected]: Point-and-click URIs for embedded
LilyPond expressions are malformed
http://code.google.com/p/lilypond/issues/detail?id=1416
Since 2.15.21, the reported problem should be fixed.
The behavior problematized in comment #1 does not appear to be solvable.
In contrast to #{...#} which has a fixed location in the source (and thus
something worth reporting), I don't see that ly:parser-include-string _can_
offer anything like that except when used with literal strings, in which
case using it is quite pointless. So I don't see that it makes sense
bothering. One could argue for leaving off all location data instead. I
don't see that this is much of an advantage, though.
I close this issue as fixed. If someone wants to make a side issue from
comment #1, feel free to do so, but I don't see that it makes much sense.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
