Re: Problem with 2.13.30?

[Phil Holmes]

"Trevor Daniels" <address@hidden> wrote in message 
news:address@hidden
> Reinhold Kainhofer wrote Monday, August 23, 2010 6:08 PM
>
>
> > Am Donnerstag, 19. August 2010, 09:43:11 schrieb Phil Holmes:
> > > "Trevor Daniels" <address@hidden> wrote in message
> > > news:address@hidden
> > >
> > > > Reinhold's refactoring of lilypond-book modules was
> > > > first included in the 2.13.24 release, so this looks
> > > > a more likely cause.  He made a series of changes
> > > > terminating in commit 7d4265883794cec4ad0e7312f0787d0565fe757f
> > > > on 11 Jun 2010.
> >
> > I have now reverted the filter_pipe function to use the deprecated 
> > os.popen3
> > again. However, if we ever resolve the subprocess/msvcrt issue in 
> > Windows, we
> > should replace all those deprecated functions by the proper "new"
> > functions....
>
> Thanks Reinhold.  I confirm the revert has fixed this problem.
> It doesn't show in 2.13.31.
>
> However, I'm now back to my original problem first reported
> in http://lists.gnu.org/archive/html/lilypond-devel/2010-07/msg00063.html
>
> Could someone else on Windows please check they see
> this problem too.  If so, I'll see if I can narrow it
> down to a specific release.
>
> Trevor

I've never tried the book functions, but can tell you what the problem is. 
Your report says:

snippet-map--1679029745.ly:4:57: illegal character in escape sequence: #\U


Line 4 in the snippet map is
#(ly:add-file-name-alist '(("3e/lily-0cba8859.ly" . 
"C:\Users\Trevor\LilyPond-git\Documentation\music-glossary.tely")


so it honks on the \ after C:\.
There's a straight quote of the filename, which in windows uses a backslash: 
\  (in Unix, I think the directory separator is a forward slash: /). 
Backslash is also used to denote a control character, so \n is a newline, 
for example.  So the interpreter is trying to view \U as a control 
character, which is not, so it barfs.  The normal fix is to make each 
backslash a double: C:\\Users\\Trevor etc.  Dunno if this is helpful, but 
that's what I think is happening.

--
Phil Holmes
Bug Squad