Re: Issue 1416 in lilypond: Point-and-click URIs for embedded LilyPond expressions are malformed

[lilypond]

Comment #1 on issue 1416 by n.puttock: Point-and-click URIs for embedded  
LilyPond expressions are malformed
http://code.google.com/p/lilypond/issues/detail?id=1416

You'll also get the same problem (with a slightly different URI, <included  
string>) when using ly:parser-include-string:

#(ly:parser-include-string parser "{ c'4 }")

textedit:///home/neil/%3cincluded%20string%3e:1:2:2

Both this function and ly:parser-parse-string (which the hash extend  
function uses to parse LilyPond code from scheme) cause the lexer to create  
new input (hence the dummy file names).