[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with 2.13.30?

From: Trevor Daniels
Subject: Re: Problem with 2.13.30?
Date: Thu, 26 Aug 2010 10:04:15 +0100

"Phil Holmes" <address@hidden> wrote in message news:address@hidden
"Trevor Daniels" <address@hidden> wrote in message news:address@hidden

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.


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.

Your explanation is pretty close.  The snippet map in
Windows should contain forward slashes rather than
escaped ones.

Here's what happens now with various releases.

2.13.23 and earlier

Snippet map contains forward slashes, so no problem

2.13.24 - 2.13.29

lilypondbook fails with pipe problem now, see
so no snippet map is produced.  (This seems to depend
on past history or my system as 2.13.26 on one occasion
got further and failed with the snippet map containing
backslashes, and IIRC Eluze reported the msvcrt problem
in this release.)


lilypondbook fails with msvcrt problem, fixed in 2.13.31


Snippet map contains backward slashes, so fails


reply via email to

[Prev in Thread] Current Thread [Next in Thread]