Problem with 2.13.30?
The mingw binary of 2.13.30 gives the following error under Vista on my system: Running lilypond-book Traceback (most recent call last): File "c:/program files/lilypond/usr/bin/lilypond-book.py", line 86, in ? import book_base as BookBase File "out/book_base.py", line 4, in ? File "out/book_snippets.py", line 9, in ? File "c:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py", line 352, in ? import msvcrt ImportError: No module named msvcrt Lilypond-book returned code 1 Could someone else please try this to see if this is a problem with the release or my system. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
On Sat, Aug 14, 2010 at 4:10 PM, Trevor Daniels wrote: > The mingw binary of 2.13.30 gives the following error > under Vista on my system: > > Running lilypond-book > Traceback (most recent call last): > File "c:/program files/lilypond/usr/bin/lilypond-book.py", line 86, in ? > import book_base as BookBase > File "out/book_base.py", line 4, in ? > File "out/book_snippets.py", line 9, in ? > File "c:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py", line 352, > in > ? > import msvcrt > ImportError: No module named msvcrt > Lilypond-book returned code 1 > > Could someone else please try this to see if this is a > problem with the release or my system. I can reproduce the problem with Wine, running the following: $ wine python.exe lilypond-book.py I've never tried this before, so I don't know whether or not this worked with 2.11.29 or earlier. -Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
On 8/14/10 5:10 PM, "Trevor Daniels" wrote: > The mingw binary of 2.13.30 gives the following error > under Vista on my system: > > Running lilypond-book > Traceback (most recent call last): > File "c:/program files/lilypond/usr/bin/lilypond-book.py", line > 86, in ? > import book_base as BookBase > File "out/book_base.py", line 4, in ? > File "out/book_snippets.py", line 9, in ? > File "c:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py", > line 352, in > ? > import msvcrt > ImportError: No module named msvcrt > Lilypond-book returned code 1 > > Could someone else please try this to see if this is a > problem with the release or my system. I don't have a GUB release, but my local build of 2.13.30 works just fine on OSX 10.5 Of course, that's what I'd expect -- OSX shouldn't be looking for msvcrt. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
hello On 8/15/2010 12:10 AM, Trevor Daniels wrote: The mingw binary of 2.13.30 gives the following error under Vista on my system: Running lilypond-book Traceback (most recent call last): File "c:/program files/lilypond/usr/bin/lilypond-book.py", line 86, in ? import book_base as BookBase File "out/book_base.py", line 4, in ? File "out/book_snippets.py", line 9, in ? File "c:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py", line 352, in ? import msvcrt ImportError: No module named msvcrt Lilypond-book returned code 1 Could someone else please try this to see if this is a problem with the release or my system. Ditto Windows 7. But I've never run lilypond-book before. So i cannot tell you if it was in 2.13.2x. James ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
On Sat, Aug 14, 2010 at 5:23 PM, Patrick McCarty wrote: > On Sat, Aug 14, 2010 at 4:10 PM, Trevor Daniels wrote: >> The mingw binary of 2.13.30 gives the following error >> under Vista on my system: >> >> Running lilypond-book >> Traceback (most recent call last): >> File "c:/program files/lilypond/usr/bin/lilypond-book.py", line 86, in ? >> import book_base as BookBase >> File "out/book_base.py", line 4, in ? >> File "out/book_snippets.py", line 9, in ? >> File "c:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py", line 352, >> in >> ? >> import msvcrt >> ImportError: No module named msvcrt >> Lilypond-book returned code 1 >> >> Could someone else please try this to see if this is a >> problem with the release or my system. > > I can reproduce the problem with Wine, running the following: > > $ wine python.exe lilypond-book.py > > I've never tried this before, so I don't know whether or not this > worked with 2.11.29 or earlier. One further note: This could be related to Jan's recent changes to the MinGW Python build in GUB. Something related to "msvcrt" was added here: http://github.com/janneke/gub/commit/e3d46689d881045ceb2dbf31d7d4573709f781d8#L1R136 Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Patrick McCarty wrote Sunday, August 15, 2010 7:27 AM On Sat, Aug 14, 2010 at 5:23 PM, Patrick McCarty wrote: On Sat, Aug 14, 2010 at 4:10 PM, Trevor Daniels wrote: The mingw binary of 2.13.30 gives the following error under Vista on my system: Running lilypond-book Traceback (most recent call last): File "c:/program files/lilypond/usr/bin/lilypond-book.py", line 86, in ? import book_base as BookBase File "out/book_base.py", line 4, in ? File "out/book_snippets.py", line 9, in ? File "c:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py", line 352, in ? import msvcrt ImportError: No module named msvcrt Lilypond-book returned code 1 Could someone else please try this to see if this is a problem with the release or my system. I can reproduce the problem with Wine, running the following: $ wine python.exe lilypond-book.py I've never tried this before, so I don't know whether or not this worked with 2.11.29 or earlier. One further note: This could be related to Jan's recent changes to the MinGW Python build in GUB. Something related to "msvcrt" was added here: http://github.com/janneke/gub/commit/e3d46689d881045ceb2dbf31d7d4573709f781d8#L1R136 Hhm, looks suspicious, but I'm out of my depth here. Earlier recent GUB releases gave a different problem which I reported to the bug list on 7 July: http://lists.gnu.org/archive/html/bug-lilypond/2010-07/msg00060.html Graham thought this might have been caused by Reinhold's refactoring of lilypond-book. For my LilyPond work since then I've used lilypond-book from 2.13.14, which still works fine. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Trevor Daniels wrote: > > The mingw binary of 2.13.30 gives the following error > under Vista on my system: > > Running lilypond-book > Traceback (most recent call last): > File "c:/program files/lilypond/usr/bin/lilypond-book.py", line > 86, in ? > import book_base as BookBase > File "out/book_base.py", line 4, in ? > File "out/book_snippets.py", line 9, in ? > File "c:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py", > line 352, in > ? > import msvcrt > ImportError: No module named msvcrt > Lilypond-book returned code 1 > 2.13.23 is fine whereas 2.13.25 + higher have the above messages ( i haven't loaded 2.13.24)! -- View this message in context: http://old.nabble.com/Problem-with-2.13.30--tp29439728p29441287.html Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Eluze wrote Sunday, August 15, 2010 10:20 AM Trevor Daniels wrote: The mingw binary of 2.13.30 gives the following error under Vista on my system: Running lilypond-book Traceback (most recent call last): File "c:/program files/lilypond/usr/bin/lilypond-book.py", line 86, in ? import book_base as BookBase File "out/book_base.py", line 4, in ? File "out/book_snippets.py", line 9, in ? File "c:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py", line 352, in ? import msvcrt ImportError: No module named msvcrt Lilypond-book returned code 1 2.13.23 is fine whereas 2.13.25 + higher have the above messages ( i haven't loaded 2.13.24)! Thanks Eluze. To help track this down, 2.13.23 was built on 3 Jun 2010 2.13.24 was built on 14 Jun 2010 2.13.25 was built on 20 Jun 2010 Jan's change to MinGW as reported by Patrick: This could be related to Jan's recent changes to the MinGW Python build in GUB. Something related to "msvcrt" was added here: http://github.com/janneke/gub/commit/e3d46689d881045ceb2dbf31d7d4573709f781d8#L1R136 was made on 18 Jul 2010, so this can't be the cause. 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. Bug-squad: can you please raise an issue for this. lilypond-book in the MinGW release is currently unusable. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Am Donnerstag, 19. August 2010, 09:43:11 schrieb Phil Holmes: > "Trevor Daniels" wrote in message > news:3df57d198d544514adecfbe3c1278...@trevorlaptop... > > > Eluze wrote Sunday, August 15, 2010 10:20 AM > > > >> Trevor Daniels wrote: > >>> The mingw binary of 2.13.30 gives the following error > >>> under Vista on my system: [...] > >>> File "out/book_base.py", line 4, in ? > >>> File "out/book_snippets.py", line 9, in ? > >>> File "c:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py", > >>> line 352, in ? > >>> import msvcrt > >>> > >>> ImportError: No module named msvcrt > >>> Lilypond-book returned code 1 [...] > > 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. The filter_pipe function used os.popen3, which according to the python documentation has been deprecated since python 2.6: http://docs.python.org/library/os.html The suggested replacement is subprocess.Popen, see also http://docs.python.org/release/2.4/lib/node238.html and http://docs.python.org/release/2.4/lib/module-subprocess.html. In windows, the subprocess module needs the msvcrt python module, which is part of the python standard lib since 2.4: http://docs.python.org/release/2.4/lib/module- msvcrt.html Unfortunately, it seems that in GUB, python is not built with that python module, so of course the subprocess module refuses to laod. 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 Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Reinhold Kainhofer wrote Monday, August 23, 2010 6:08 PM Am Donnerstag, 19. August 2010, 09:43:11 schrieb Phil Holmes: "Trevor Daniels" wrote in message news:3df57d198d544514adecfbe3c1278...@trevorlaptop... > 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 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
"Phil Holmes" wrote in message
news:i53pqa$tp...@dough.gmane.org...
"Trevor Daniels" wrote in message
news:305ede3e0e3f4cdc926db8734c558...@trevorlaptop...
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.
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
http://lists.gnu.org/archive/html/bug-lilypond/2010-07/msg00060.html
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.)
2.13.30
lilypondbook fails with msvcrt problem, fixed in 2.13.31
2.13.31
Snippet map contains backward slashes, so fails
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Am Donnerstag, 26. August 2010, um 11:04:15 schrieb Trevor Daniels:
> "Phil Holmes" wrote in message
> news:i53pqa$tp...@dough.gmane.org...
> > 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")
[...]
> Your explanation is pretty close. The snippet map in
> Windows should contain forward slashes rather than
> escaped ones.
Thanks, Trevor, for you bisecting... The culprit is actually not the
refactoring, but a bug fix I did before the refactoring (commit
4da9fc65cbf74f4cbbdb01add4d5f341a16f5065 at 10.06.10 13:01).
The problem I fixed with it was quite ugly (and I wonder why noone ever ran
into it and complained): If your want to run lilypond-book on a file with
*.tex, *.html or *.texi extension, you need to use the --output option,
because otherwise the input file would be named the same and the input file
would be overwritten.
Unfortunately, in this particular case (where the file name of the input and
the output file was the same), the check for input==output file was terribly
broken. Try it out by creating a file test.tex and run
lilypond-book --output=out test.tex
on it. The first time, it will work and create out/test.tex, but the second
time it will complain that the output file is the same as the input file
(which it is not!) and refuse to work on the file.
In that case, the input filename is simply test.tex, and the output filename
is C:/path/to/out/test.tex. The problem was that sooner or later the lilypond-
book script changed the current directory to the output directory (after
reading in the input file's contents). As a consequence the input filename
"test.tex" was now taken relative to the output filename, and then the input
and output filenames were really identical.
As a solution, I changed the input filename from a relative path (which causes
problems as soon as the current working dir is changed in a script) to an
absolute path by calling os.path.abspath (...).
Unfortunately, os.path.abspath (...) on Windows has the side-effect of
changing all / to \. See http://docs.python.org/library/os.path.html
I don't really see any other way to turn the input path to an absolute path
than calling os.path.abspath, in particular, since the input path can already
be an absolute path...
Cheers,
Reinhold
I don't remember how to reproduce the problem, but the issue was that with
some files containing include files (involving subdirectories somehow), some
output pathes were taken relative to the current working directory.
Now, the lilypond-book at some point changed the working directory to the
output directory, so those paths were suddenly taken relative to the output
directory rather than the input directory.
As a solution, I
>
> 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
> http://lists.gnu.org/archive/html/bug-lilypond/2010-07/msg00060.html
> 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.)
>
> 2.13.30
>
> lilypondbook fails with msvcrt problem, fixed in 2.13.31
>
> 2.13.31
>
> Snippet map contains backward slashes, so fails
>
> Trevor
>
>
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Reinhold Kainhofer wrote Sunday, August 29, 2010 8:33 PM Thanks, Trevor, for you bisecting... The culprit is actually not the refactoring, but a bug fix I did before the refactoring (commit 4da9fc65cbf74f4cbbdb01add4d5f341a16f5065 at 10.06.10 13:01). The problem I fixed with it was quite ugly (and I wonder why noone ever ran into it and complained): If your want to run lilypond-book on a file with *.tex, *.html or *.texi extension, you need to use the --output option, because otherwise the input file would be named the same and the input file would be overwritten. [snip description of problem] As a solution, I changed the input filename from a relative path (which causes problems as soon as the current working dir is changed in a script) to an absolute path by calling os.path.abspath (...). Unfortunately, os.path.abspath (...) on Windows has the side-effect of changing all / to \. See http://docs.python.org/library/os.path.html I don't really see any other way to turn the input path to an absolute path than calling os.path.abspath, in particular, since the input path can already be an absolute path... But doesn't this solution create a worse problem than the original one? With this fix lilypondbook cannot be used *at all* under Windows. The original problem has a simple workaround which could be documented easily - the problem created by the fix has no workaround. I have to copy an old version of lilypondbook into every new release in order to get a working version. We can't expect users to do that. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
On Sun, Aug 29, 2010 at 11:25:47PM +0100, Trevor Daniels wrote: > > I have to copy an old version of > lilypondbook into every new release in order to get > a working version. We can't expect users to do that. I'm confused about what's going on. Are you talking about 1226 (which is claimed to be Fixed), or is this a different problem, which was never added to the tracker? We currently have 5 officially open Critical issues; that is the information I consider when planning releases. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Graham Percival wrote Monday, August 30, 2010 12:02 AM On Sun, Aug 29, 2010 at 11:25:47PM +0100, Trevor Daniels wrote: I have to copy an old version of lilypondbook into every new release in order to get a working version. We can't expect users to do that. I'm confused about what's going on. Are you talking about 1226 (which is claimed to be Fixed), or is this a different problem, which was never added to the tracker? This is a different problem which hasn't (yet) been added to the tracker. I first asked on -dev if anyone else had seen it: http://lists.gnu.org/archive/html/lilypond-devel/2010-07/msg00063.html It was then masked for a time by 1226, and reappeared when this was fixed. I then reported it on -bug: http://lists.gnu.org/archive/html/bug-lilypond/2010-08/msg00480.html I've not added it to the tracker myself as no one else had confirmed it until Reinhold pointed to the source of the problem today: http://lists.gnu.org/archive/html/bug-lilypond/2010-08/msg00533.html So it should be added to the tracker now. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Am Montag, 30. August 2010, um 00:25:47 schrieben Sie: > > I don't really see any other way to turn the input path to an > > absolute path > > than calling os.path.abspath, in particular, since the input path > > can already > > be an absolute path... > > But doesn't this solution create a worse problem > than the original one? With this fix lilypondbook > cannot be used *at all* under Windows. The original > problem has a simple workaround which could be documented > easily - the problem created by the fix has no > workaround. Yes, I see the problem... On the other hand, without this fix, lilypond-book is not able to work with *.tex, *.html or *.texi input files at all (the bug is that when --output is given, then that wrong error message is triggered and lilypond-book refuses to work). There is also no workaround for this, except discouraging the use of these three extensions at all for input files :( > I have to copy an old version of > lilypondbook into every new release in order to get > a working version. We can't expect users to do that. No, of course not. I'm thinking about how to make l-p work for both cases. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Am Montag, 30. August 2010, 01:48:46 schrieb Reinhold Kainhofer: > Am Montag, 30. August 2010, um 00:25:47 schrieben Sie: > > > I don't really see any other way to turn the input path to an > > > absolute path > > > than calling os.path.abspath, in particular, since the input path > > > can already > > > be an absolute path... > > > > But doesn't this solution create a worse problem > > than the original one? With this fix lilypondbook > > cannot be used *at all* under Windows. The original > > problem has a simple workaround which could be documented > > easily - the problem created by the fix has no > > workaround. > > Yes, I see the problem... > On the other hand, without this fix, lilypond-book is not able to work with > *.tex, *.html or *.texi input files at all (the bug is that when --output > is given, then that wrong error message is triggered and lilypond-book > refuses to work). > There is also no workaround for this, except discouraging the use of these > three extensions at all for input files :( > > > I have to copy an old version of > > lilypondbook into every new release in order to get > > a working version. We can't expect users to do that. > > No, of course not. I'm thinking about how to make l-p work for both cases. Should be fixed in git now. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Reinhold Kainhofer wrote Monday, September 06, 2010 8:29 PM Am Montag, 30. August 2010, 01:48:46 schrieb Reinhold Kainhofer: Am Montag, 30. August 2010, um 00:25:47 schrieben Sie: > > I don't really see any other way to turn the input path to an > > absolute path > > than calling os.path.abspath, in particular, since the input > > path > > can already > > be an absolute path... > > But doesn't this solution create a worse problem > than the original one? With this fix lilypondbook > cannot be used *at all* under Windows. The original > problem has a simple workaround which could be documented > easily - the problem created by the fix has no > workaround. Yes, I see the problem... Should be fixed in git now. Looks good to me. I'll confirm when the GUB 2.13.33 for Windows is available. Thanks, Reinhold! Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
On Tue, Sep 7, 2010 at 1:01 AM, Trevor Daniels wrote: > Looks good to me. I'll confirm when the GUB > 2.13.33 for Windows is available. Greetings Trevor, sorry for bumping this discussion, but: where are we wrt this problem? Do we need to open a tracker page about it? http://lists.gnu.org/archive/html/lilypond-devel/2010-08/msg00346.html Thanks! Valentin. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
Valentin Villenave wrote Sunday, October 17, 2010 4:57 PM On Tue, Sep 7, 2010 at 1:01 AM, Trevor Daniels wrote: Looks good to me. I'll confirm when the GUB 2.13.33 for Windows is available. sorry for bumping this discussion, but: where are we wrt this problem? Whoops, sorry, I forgot to report this. Reinhold's patch did fix it. Do we need to open a tracker page about it? No need now. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with 2.13.30?
On Sun, Oct 17, 2010 at 7:52 PM, Trevor Daniels wrote: > No need now. Very well then, thanks for the follow-up! Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
