Re: LilyPond-Book on Windows
I just tried rerunning lilypond-book after changing the temp directory
to something simpler. That has run successfully, mostly. There were no
errors thrown by either lilypond-book or pdflatex, but the snippet
widths did not fit the page properly. The contents of the commandline
follow:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Admincd c:\tmp
C:\tmpset TEMP=c:\temp
C:\tmplilypond-book test.lytex
lilypond-book.py (GNU LilyPond) 2.19.4
Reading test.lytex...
Running `latex' on file `c:\temp\tmpt5-2t3.tex' to detect default page settings.
lilypond-book.py: warning: Unable to auto-detect default settings:
lilypond-book.py: warning: cannot detect textwidth from LaTeX
Dissecting...
Writing snippets...
Processing...
Running lilypond...
GNU LilyPond 2.19.4
programming error: file name not normalized: C:\tmp\snippet-names-1571787863.ly
continuing, cross fingers
Processing `snippet-map-1571787863.ly'
Parsing...
Processing `test.lytex'
Parsing...
Interpreting music...[8][8]
Preprocessing graphical objects...
Calculating line breaks...
Drawing systems...
Layout output to `f6/lily-b39ab8e8.eps'...
Layout output to `f6/lily-b39ab8e8-1.eps'...
Layout output to `f6/lily-b39ab8e8-2.eps'...
Layout output to `f6/lily-b39ab8e8-3.eps'...
Writing f6/lily-b39ab8e8-systems.texi...
Writing f6/lily-b39ab8e8-systems.tex...
Writing f6/lily-b39ab8e8-systems.count...
Success: compilation successfully completed
Linking files...
Compiling C:\tmp\test.tex...
Writing `C:\tmp\test.tex'...
C:\tmppdflatex test.tex
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/W32TeX)
restricted \write18 enabled.
entering extended mode
(./test.tex
LaTeX2e 2011/06/27
Babel 3.9k and hyphenation patterns for 78 languages loaded.
(c:/texlive/2013/texmf-dist/tex/latex/base/report.cls
Document Class: report 2007/10/19 v1.4h Standard LaTeX document class
(c:/texlive/2013/texmf-dist/tex/latex/base/size12.clo))
(c:/texlive/2013/texmf-dist/tex/latex/graphics/graphics.sty
(c:/texlive/2013/texmf-dist/tex/latex/graphics/trig.sty)
(c:/texlive/2013/texmf-dist/tex/latex/latexconfig/graphics.cfg)
(c:/texlive/2013/texmf-dist/tex/latex/pdftex-def/pdftex.def
(c:/texlive/2013/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(c:/texlive/2013/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)))
No file test.aux.
(c:/texlive/2013/texmf-dist/tex/context/base/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
) (c:/texlive/2013/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty
(c:/texlive/2013/texmf-dist/tex/generic/oberdiek/ifluatex.sty)
(c:/texlive/2013/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
(c:/texlive/2013/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
(c:/texlive/2013/texmf-dist/tex/latex/oberdiek/grfext.sty
(c:/texlive/2013/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty))
(c:/texlive/2013/texmf-dist/tex/latex/oberdiek/kvoptions.sty
(c:/texlive/2013/texmf-dist/tex/latex/graphics/keyval.sty)
(c:/texlive/2013/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
(c:/texlive/2013/texmf-dist/tex/generic/oberdiek/etexcmds.sty)))
(c:/texlive/2013/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg))
(./f6/lily-b39ab8e8-systems.tex
f6/lily-b39ab8e8-1-eps-converted-to.pdf, id=1, 548.0475pt x 78.2925pt
use f6/lily-b39ab8e8-1-eps-converted-to.pdf
f6/lily-b39ab8e8-2-eps-converted-to.pdf, id=2, 548.0475pt x 51.19125pt
use f6/lily-b39ab8e8-2-eps-converted-to.pdf
f6/lily-b39ab8e8-3-eps-converted-to.pdf, id=3, 548.0475pt x 50.1875pt
use f6/lily-b39ab8e8-3-eps-converted-to.pdf)
Overfull \hbox (158.04616pt too wide) in paragraph at lines 15--27
[]
Overfull \hbox (158.04616pt too wide) in paragraph at lines 15--27
[]
Overfull \hbox (158.04616pt too wide) in paragraph at lines 15--27
[]
Underfull \hbox (badness 1) in paragraph at lines 15--27
(c:/texlive/2013/texmf-dist/tex/latex/base/omscmr.fd) [1{c:/texlive/2013/texmf-
var/fonts/map/pdftex/updmap/pdftex.map} ./f6/lily-b39ab8e8-1-eps-converted-to.
pdf ./f6/lily-b39ab8e8-2-eps-converted-to.pdf ./f6/lily-b39ab8e8-3-eps-conv
erted-to.pdf] (./test.aux) )
(see the transcript file for additional information)c:/texlive/2013/texmf-dist
/fonts/type1/public/amsfonts/cm/cmr10.pfbc:/texlive/2013/texmf-dist/fonts/typ
e1/public/amsfonts/cm/cmr12.pfbc:/texlive/2013/texmf-dist/fonts/type1/public/
amsfonts/cm/cmsy10.pfbc:/texlive/2013/texmf-dist/fonts/type1/public/amsfonts/
cm/cmti10.pfbc:/texlive/2013/texmf-dist/fonts/type1/urw/ncntrsbk/uncb8a.pfb
c:/texlive/2013/texmf-dist/fonts/type1/urw/ncntrsbk/uncr8a.pfb
Output written on test.pdf (1 page, 90811 bytes).
Transcript written on test.log.
C:\tmp
A second trial with lualatex still caused the hanging error. The
contents of that command line:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Admincd c:\tmp
C:\tmpset TEMP=c:\temp
C:\tmplilypond-book --latex-program lualatex test.lytex
lilypond-book.py (GNU LilyPond) 2.19.4
Reading test.lytex...
Re: LilyPond-Book on Windows
Br. Samuel Springuel rpspring...@gmail.com writes: I just downloaded the lilypond 2.19.4 windows binary and I'm not seeing any change in the behavior of lilypond-book. I don't know if this is worth anything, but I have not been having lilypond-book hang with 2.19.3, but due to a different problem, I tried changing to 2.19.4, and now the same files and command line result in what appears to be a hung python. At any rate, it sits for longer than my meager patience can withstand. This is on Windows 7 Professional, service pack 1, and it is the Python version 2.5.4 that came with Lilypond. I am probably not clever enough to provide further useful information without prompting, but would be quite happy to be prompted. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Evans Winner ego...@gmail.com writes: [...] and it is the Python version 2.5.4 that came Excuse me, I meant 2.4.5. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: python 2.6 in GUB Re: LilyPond-Book on Windows
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: David Kastrup d...@gnu.org
Cc: Jan Nieuwenhuizen jann...@gnu.org; Phil Holmes
m...@philholmes.net; Br. Samuel Springuel rpspring...@gmail.com;
lilypond-user@gnu.org; Julien Rioux julien.ri...@gmail.com
Sent: Sunday, April 06, 2014 2:42 AM
Subject: python 2.6 in GUB Re: LilyPond-Book on Windows
On Sat, Apr 05, 2014 at 08:53:04AM +0200, David Kastrup wrote:
Jan Nieuwenhuizen jann...@gnu.org writes:
David Kastrup writes:
So my first impulse would be to throw out the workaround for 2.4.2
that
Let's do that.
Well, issue 1933
URL:http://code.google.com/p/lilypond/issues/detail?id=1933 would
suggest that this is a bad idea. Nothing substantially has changed
since then. I'm currently trying to get the TEXINPUTS stuff integrated
into the Mingw fix to arrive back at a working lilypond-book, but of
course it is to be hoped that moving Python forward to 2.6 might make
that problem go away. But it will take longer to figure that out.
Doesn't Julien have GUB with python 2.6 ready for testing? I
would move forward on that before diving into the dark waters of
os.popen in python 2.4. I remember bug 1933; it was really
annoying.
Cheers,
- Graham
I pulled Julien's branch directly from his repo in order to update my
version of GUB to his version with Python 2.6. The LilyPond build failed,
with the error listing below. I've got the full python.log if needed.
*** Stage: compile (python, freebsd-x86)
*** Stage: install (python, freebsd-x86)
all python modules:_elementtree.so, imageop.so, _testcapi.so, array.so,
itertools.so, _bsddb.so, crypt.so, _bytesio.so, _multiprocessing.so,
_csv.so, _struct.so, ossaudiodev.so, _weakref.so, select.so, mmap.so, dl.so,
parser.so, _hotshot.so, _lsprof.so, _random.so, grp.so, _codecs_kr.so,
_codecs_tw.so, _codecs_cn.so, _codecs_jp.so, operator.so, _heapq.so,
_socket.so, _collections.so, _sha512.so, pyexpat.so, dbm.so, cPickle.so,
fcntl.so, resource.so, _ctypes.so, unicodedata.so, _codecs_hk.so, syslog.so,
termios.so, cStringIO.so, _bisect.so, _sha256.so, _locale.so, _functools.so,
_codecs_iso2022.so, _json.so, _ctypes_test.so, _fileio.so,
_multibytecodec.so, future_builtins.so, nis.so, strop.so, _md5.so, _sha.so,
audioop.so
Tail of target/freebsd-x86/log/python.log
Running chmod
('/home/gub/gub/target/freebsd-x86/install/python-2.6.4-root/usr/cross/bin/python-config',
493)
{}
invoking assert_fine ()
all python modules:_elementtree.so, imageop.so, _testcapi.so, array.so,
itertools.so, _bsddb.so, crypt.so, _bytesio.so, _multiprocessing.so,
_csv.so, _struct.so, ossaudiodev.so, _weakref.so, select.so, mmap.so, dl.so,
parser.so, _hotshot.so, _lsprof.so, _random.so, grp.so, _codecs_kr.so,
_codecs_tw.so, _codecs_cn.so, _codecs_jp.so, operator.so, _heapq.so,
_socket.so, _collections.so, _sha512.so, pyexpat.so, dbm.so, cPickle.so,
fcntl.so, resource.so, _ctypes.so, unicodedata.so, _codecs_hk.so, syslog.so,
termios.so, cStringIO.so, _bisect.so, _sha256.so, _locale.so, _functools.so,
_codecs_iso2022.so, _json.so, _ctypes_test.so, _fileio.so,
_multibytecodec.so, future_builtins.so, nis.so, strop.so, _md5.so, _sha.so,
audioop.so
Tail of target/freebsd-x86/log/python.log
Traceback (most recent call last):
File bin/gub, line 233, in exceptional_build
build (settings, options, files)
File bin/gub, line 229, in build
b.build_source_packages (names)
File bin/../gub/buildrunner.py, line 334, in build_source_packages
self.spec_build (spec_name)
File bin/../gub/buildrunner.py, line 262, in spec_build
deferred_runner.execute_deferred_commands ()
File bin/../gub/runner.py, line 167, in execute_deferred_commands
cmd.execute (self.logger)
File bin/../gub/commands.py, line 172, in execute
return self.func (logger, *self.args)
File /home/gub/gub/gub/specs/python-2.4.py, line 104, in assert_fine
raise Exception ('Python module failed: ' + module)
Exception: Python module failed: datetime
*** Failed target: freebsd-x86::python
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: python 2.6 in GUB Re: LilyPond-Book on Windows
Phil Holmes m...@philholmes.net writes:
I pulled Julien's branch directly from his repo in order to update my
version of GUB to his version with Python 2.6. The LilyPond build
failed, with the error listing below. I've got the full python.log if
needed.
[...]
Running chmod
('/home/gub/gub/target/freebsd-x86/install/python-2.6.4-root/usr/cross/bin/python-config',
493)
[...]
File /home/gub/gub/gub/specs/python-2.4.py, line 104, in assert_fine
raise Exception ('Python module failed: ' + module)
Exception: Python module failed: datetime
*** Failed target: freebsd-x86::python
That seems suspicious: the specs are 2.4? I think that Jan's repository
stated throw the Python 2.6 switch somewhere. Would an equivalent of
that commit be in Julien's branch?
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: python 2.6 in GUB Re: LilyPond-Book on Windows
- Original Message -
From: David Kastrup d...@gnu.org
To: Phil Holmes m...@philholmes.net
Cc: Graham Percival gra...@percival-music.ca; Jan Nieuwenhuizen
jann...@gnu.org; lilypond-user@gnu.org; Julien Rioux
julien.ri...@gmail.com
Sent: Tuesday, April 08, 2014 3:45 PM
Subject: Re: python 2.6 in GUB Re: LilyPond-Book on Windows
Phil Holmes m...@philholmes.net writes:
I pulled Julien's branch directly from his repo in order to update my
version of GUB to his version with Python 2.6. The LilyPond build
failed, with the error listing below. I've got the full python.log if
needed.
[...]
Running chmod
('/home/gub/gub/target/freebsd-x86/install/python-2.6.4-root/usr/cross/bin/python-config',
493)
[...]
File /home/gub/gub/gub/specs/python-2.4.py, line 104, in assert_fine
raise Exception ('Python module failed: ' + module)
Exception: Python module failed: datetime
*** Failed target: freebsd-x86::python
That seems suspicious: the specs are 2.4? I think that Jan's repository
stated throw the Python 2.6 switch somewhere. Would an equivalent of
that commit be in Julien's branch?
I did wonder about that. I assume GUB is actually running 2.4 at this
point, since it seems to be compiling 2.6?
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
I just downloaded the lilypond 2.19.4 windows binary and I'm not seeing any change in the behavior of lilypond-book. Checking the included python version, and it still appears to be 2.4.5. Was this supposed to be upped to 2.6? Here's the contents of my command prompt after using the KeyboardInterrupt to stop the apparently hung process: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Admincd My Documents\Sext Hymns C:\Documents and Settings\Admin\My Documents\Sext Hymnslilypond-book --latex-pr ogram pdflatex --output C:\Documents and Settings\Admin\My Documents\Sext Hymns \test-out --lily-output-dir C:\Documents and Settings\Admin\My Documents\Sext Hymns\test-lily --verbose test.lytex lilypond-book.py: Setting LilyPond's output to --verbose, implied by lilypond-bo ok's setting lilypond-book.py (GNU LilyPond) 2.19.4 Reading test.lytex... Running `pdflatex' on file `c:\docume~1\admin\locals~1\temp\tmpaidjyx.tex' to de tect default page settings. Executing: pdflatex c:\docume~1\admin\locals~1\temp\tmpaidjyx.tex Traceback (most recent call last): File c:\Program Files\LilyPond\usr\bin\lilypond-book.py, line 776, in ? main () File c:\Program Files\LilyPond\usr\bin\lilypond-book.py, line 759, in main chunks = do_file (files[0]) File c:\Program Files\LilyPond\usr\bin\lilypond-book.py, line 607, in do_fil e global_options.formatter.init_default_snippet_options (source) File c:\Program Files\LilyPond\usr\share\lilypond\current\python\book_base.py , line 141, in init_default_snippet_options line_width = self.get_line_width (source) File c:\Program Files\LilyPond\usr\share\lilypond\current\python\book_latex.p y, line 300, in get_line_width textwidth = get_latex_textwidth (source, self.global_options) File c:\Program Files\LilyPond\usr\share\lilypond\current\python\book_latex.p y, line 212, in get_latex_textwidth returncode = os.system(cmd) KeyboardInterrupt C:\Documents and Settings\Admin\My Documents\Sext Hymns Adding the --pdf flag changes things a bit: C:\Documents and Settings\Admin\My Documents\Sext Hymnslilypond-book --latex-pr ogram pdflatex --output C:\Documents and Settings\Admin\My Documents\Sext Hy mns\test-out --lily-output-dir C:\Documents and Settings\Admin\My Documents\Se xt Hymns\test-lily --verbose --pdf test.lytex Usage: lilypond-book [OPTION]... FILE Process LilyPond snippets in hybrid HTML, LaTeX, texinfo or DocBook document. Examples: $ lilypond-book --filter=tr '[a-z]' '[A-Z]' BOOK $ lilypond-book -F convert-ly --no-version --from=2.0.0 - BOOK $ lilypond-book --process='lilypond -I include' BOOK Options: -F, --filter=FILTER pipe snippets through FILTER [default: `convert-ly -n -'] -f, --format=FORMAT use output format FORMAT (texi [default], texi-html, latex, html, docbook) -h, --help show this help and exit -I, --include=DIRadd DIR to include path --info-images-dir=DIR format Texinfo output so that Info will look for images of music in DIR --left-padding=PAD pad left side of music to align music inspite of uneven bar numbers (in mm) --lily-loglevel=LOGLEVEL Print lilypond log messages according to LOGLEVEL --lily-output-dir=DIR write lily-XXX files to DIR, link into --output dir --load-custom-package=PACKAGE Load the additional python PACKAGE (containing e.g. a custom output format) -l, --loglevel=LOGLEVEL Print log messages according to LOGLEVEL (NONE, ERROR, WARNING, PROGRESS (default), DEBUG) -o, --output=DIR write output to DIR -P, --process=COMMAND process ly_files using COMMAND FILE... --redirect-lilypond-output Redirect the lilypond output -s, --safe Compile snippets in safe mode --skip-lily-check do not fail if no lilypond output is found --skip-png-check do not fail if no PNG images are found for EPS files --use-source-file-names write snippet output files with the same base name as their source file -V, --verbosebe verbose --versionshow version number and exit -w, --warranty show warranty and copyright Options only for the latex and texinfo backends: --latex-program=PROG run executable PROG instead of latex, or in case --pdf option is set instead of pdflatex --texinfo-program=PROG run executable PROG instead of texi2pdf --pdfcreate PDF files for use with PDFTeX Report bugs via
Re: LilyPond-Book on Windows
Br. Samuel Springuel rpspring...@gmail.com writes: I just downloaded the lilypond 2.19.4 windows binary and I'm not seeing any change in the behavior of lilypond-book. Checking the included python version, and it still appears to be 2.4.5. Was this supposed to be upped to 2.6? No, this is still 2.4.5 which is supposed to be used. Here's the contents of my command prompt after using the KeyboardInterrupt to stop the apparently hung process: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Admincd My Documents\Sext Hymns C:\Documents and Settings\Admin\My Documents\Sext Hymnslilypond-book --latex-pr ogram pdflatex --output C:\Documents and Settings\Admin\My Documents\Sext Hymns \test-out --lily-output-dir C:\Documents and Settings\Admin\My Documents\Sext Hymns\test-lily --verbose test.lytex lilypond-book.py: Setting LilyPond's output to --verbose, implied by lilypond-bo ok's setting lilypond-book.py (GNU LilyPond) 2.19.4 Reading test.lytex... Running `pdflatex' on file `c:\docume~1\admin\locals~1\temp\tmpaidjyx.tex' to de tect default page settings. Executing: pdflatex c:\docume~1\admin\locals~1\temp\tmpaidjyx.tex Oh, good grief. What happens when you create a directory C:\tmp, copy the files to be processed in there, and run lilypond-book on them while in _that_ directory? On my GNU/Linux system, I can trigger the following pdflatex c:\docume~1\admin\locals~1\temp\tmpaidjyx.tex This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian) restricted \write18 enabled. entering extended mode ! I can't find file `c:docume'. to be read again \protect * c:docume~ 1adminlocals~1temptmpaidjyx.tex (Press Enter to retry, or Control-D to exit) Please type another input file name: which then hangs on an input prompt. Adding the --pdf flag changes things a bit: C:\Documents and Settings\Admin\My Documents\Sext Hymnslilypond-book --latex-pr ogram pdflatex --output C:\Documents and Settings\Admin\My Documents\Sext Hy mns\test-out --lily-output-dir C:\Documents and Settings\Admin\My Documents\Se xt Hymns\test-lily --verbose --pdf test.lytex Usage: lilypond-book [OPTION]... FILE Again: what happens when running this in c:\tmp on files placed there? Process LilyPond snippets in hybrid HTML, LaTeX, texinfo or DocBook document. This looks like something is throwing the command line into tatters. Can you please try with simpler command lines, only adding complexity by and by? And report at which moment stuff starts breaking? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
As suggested, I tried moving the test files into a directory with a simple name and got what appear to me to be identical results: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Admincd c:\tmp C:\tmplilypond-book test2.lytex lilypond-book.py (GNU LilyPond) 2.19.4 Reading test2.lytex... Running `latex' on file `c:\docume~1\admin\locals~1\temp\tmpv3qfrb.tex' to detec t default page settings. And with a little added complexity to get more useful output: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Admincd c:\tmp C:\tmplilypond-book --pdf --loglevel DEBUG test.lytex lilypond-book.py: Setting LilyPond's output to --verbose, implied by lilypond-bo ok's setting lilypond-book.py (GNU LilyPond) 2.19.4 Reading test.lytex... Running `pdflatex' on file `c:\docume~1\admin\locals~1\temp\tmppptayp.tex' to de tect default page settings. Executing: pdflatex c:\docume~1\admin\locals~1\temp\tmppptayp.tex The processes have apparently hung as before. One last variation, with the same results (though this time including the output after using the KeyboardInterrupt on the process (it's the same for the two above): Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Admincd c:\tmp C:\tmplilypond-book --latex-program pdflatex --pdf test.lytex lilypond-book.py (GNU LilyPond) 2.19.4 Reading test.lytex... Running `pdflatex' on file `c:\docume~1\admin\locals~1\temp\tmpygq6ao.tex' to de tect default page settings. Traceback (most recent call last): File c:\Program Files\LilyPond\usr\bin\lilypond-book.py, line 776, in ? main () File c:\Program Files\LilyPond\usr\bin\lilypond-book.py, line 759, in main chunks = do_file (files[0]) File c:\Program Files\LilyPond\usr\bin\lilypond-book.py, line 607, in do_fil e global_options.formatter.init_default_snippet_options (source) File c:\Program Files\LilyPond\usr\share\lilypond\current\python\book_base.py , line 141, in init_default_snippet_options line_width = self.get_line_width (source) File c:\Program Files\LilyPond\usr\share\lilypond\current\python\book_latex.p y, line 300, in get_line_width textwidth = get_latex_textwidth (source, self.global_options) File c:\Program Files\LilyPond\usr\share\lilypond\current\python\book_latex.p y, line 212, in get_latex_textwidth returncode = os.system(cmd) KeyboardInterrupt C:\tmp If needed I can test other variations to try and duplicate the other error. ✝ Br. Samuel (R. Padraic Springuel) PAX ☧ ΧΡΙΣΤΟΣ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
As I was closing windows I noticed a texput.log file in the temporary directory which I hadn't seen before. It's contents: This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/W32TeX) (format=pdflatex 2014.3.29) 8 APR 2014 19:55 entering extended mode restricted \write18 enabled. %-line parsing enabled. **c:/docume~1/admin/locals~1/temp/tmpygq6ao.tex ! Emergency stop. to be read again \protect * c:/docume~ 1/admin/locals~1/temp/tmpygq6ao.tex End of file on the terminal! Here is how much of TeX's memory you used: 4 strings out of 493308 110 string characters out of 6141361 52434 words of memory out of 500 3564 multiletter control sequences out of 15000+60 3640 words of font info for 14 fonts, out of 800 for 9000 957 hyphenation exceptions out of 8191 3i,0n,0p,1b,6s stack positions out of 5000i,500n,1p,20b,8s ! == Fatal error occurred, no output PDF file produced! Based on the filename inside the log, this file goes with the third test. Running the first two tests again produced a basically identical files. The only difference was the reported file name (which appears to vary with every trial anyway) and for the first test (which did not specify pdflatex or the --pdf option) the last line was No pages of output. instead of the last line shown above. ✝ Br. Samuel (R. Padraic Springuel) PAX ☧ ΧΡΙΣΤΟΣ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Br. Samuel Springuel rpspring...@gmail.com writes: As suggested, I tried moving the test files into a directory with a simple name and got what appear to me to be identical results: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Admincd c:\tmp C:\tmplilypond-book test2.lytex lilypond-book.py (GNU LilyPond) 2.19.4 Reading test2.lytex... Running `latex' on file `c:\docume~1\admin\locals~1\temp\tmpv3qfrb.tex' to detec t default page settings. What causes lilypond-book to use such a complex directory name for the temporary file name? I rather suspect that the ~ characters in the shortened file name are the problem here. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
The ~ is what Windows uses to create short names in their file structure. For instance: c:\docume~1\admin\locals~1\temp\tmpv3qfrb.tex Refers to C:\Documents and Settings\Admin\Local Settings\Temp\tmpv3qfrb.tex In this example, Documents and Settings has been shortened to docuem~1 and Local Settings to locals~1. In both cases this is the first 6 non-space characters in the long name plus ~ plus a number (which is varied if there is more than one folder for which the first 6 non-space characters in the long name are identical). Folders with names 8 characters long or less are not affected by the shortening process except to remove spaces. While I'm not entirely sure why lilypond-book is using them, I suspect it probably has something to do with the fact that this path points to the default temporary directory. On all Windows operating systems the temporary directory is localized within the user profile. In XP, it looks like the above. In Vista, 7, and 8 it would be C:\Users\User Name\AppData\Local\Temp. If you want to avoid those temporary directories, it is possible to change the temporary directory by changing the value of the environment variable TEMP. From the command line (or in a batch file) this would be done with: SET TEMP=C:\whatever\path\you\want Do you want me to try running the lilypond-book commands again after switching the temporary directory to a simpler path? ✝ Br. Samuel (R. Padraic Springuel) PAX ☧ ΧΡΙΣΤΟΣ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Br. Samuel Springuel rpspring...@gmail.com writes: Sorry if this is a double, but I hit the wrong reply button on the first one. On 2014-04-03 8:44 AM, David Kastrup wrote: It would appear that the above code using subprocess.Popen will most likely make lilypond-book hang on Windows for essentially unknown reasons. Any idea what your Python version is? The conversation seems to have moved beyond this, but LilyPond delivered Python 2.4.5 on my machine. Try with the just released LilyPond 2.19.4. If that's more successful, we'll port the fix to 2.18. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
David, you wrote Monday, April 07, 2014 10:22 AM Try with the just released LilyPond 2.19.4. If that's more successful, we'll port the fix to 2.18. Just to confirm, lilypond-book in 2.19.4 works fine here. I.e. no change in the parts I use from 2.19.3 AFAICS. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Trevor Daniels t.dani...@treda.co.uk writes: David, you wrote Monday, April 07, 2014 10:22 AM Try with the just released LilyPond 2.19.4. If that's more successful, we'll port the fix to 2.18. Just to confirm, lilypond-book in 2.19.4 works fine here. I.e. no change in the parts I use from 2.19.3 AFAICS. No change would be not what we were aiming for with regard to LaTeX output. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
David, you wrote Monday, April 07, 2014 11:20 AM Trevor Daniels t.dani...@treda.co.uk writes: David, you wrote Monday, April 07, 2014 10:22 AM Try with the just released LilyPond 2.19.4. If that's more successful, we'll port the fix to 2.18. Just to confirm, lilypond-book in 2.19.4 works fine here. I.e. no change in the parts I use from 2.19.3 AFAICS. No change would be not what we were aiming for with regard to LaTeX output. Indeed, but that's for someone else to check - I don't use LaTeX. I was merely confirming the change did not break anything for me. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: python 2.6 in GUB Re: LilyPond-Book on Windows
- Original Message - From: Graham Percival gra...@percival-music.ca To: David Kastrup d...@gnu.org Cc: Jan Nieuwenhuizen jann...@gnu.org; Phil Holmes m...@philholmes.net; Br. Samuel Springuel rpspring...@gmail.com; lilypond-user@gnu.org; Julien Rioux julien.ri...@gmail.com Sent: Sunday, April 06, 2014 2:42 AM Subject: python 2.6 in GUB Re: LilyPond-Book on Windows On Sat, Apr 05, 2014 at 08:53:04AM +0200, David Kastrup wrote: Jan Nieuwenhuizen jann...@gnu.org writes: David Kastrup writes: So my first impulse would be to throw out the workaround for 2.4.2 that Let's do that. Well, issue 1933 URL:http://code.google.com/p/lilypond/issues/detail?id=1933 would suggest that this is a bad idea. Nothing substantially has changed since then. I'm currently trying to get the TEXINPUTS stuff integrated into the Mingw fix to arrive back at a working lilypond-book, but of course it is to be hoped that moving Python forward to 2.6 might make that problem go away. But it will take longer to figure that out. Doesn't Julien have GUB with python 2.6 ready for testing? I would move forward on that before diving into the dark waters of os.popen in python 2.4. I remember bug 1933; it was really annoying. Cheers, - Graham I should be able to test GUB with Julien's Python 2.6 later this week. I'd just like to check the process. I click the Merge pull request at https://github.com/gperciva/gub/pull/6 and this pushes Julien's changes into the GUB repo? I then pull the GUB repo on my GUB VM and this will get the changes into my version of GUB? I then make lilypond as usual. What if it doesn't work? We then need to test the built binaries: should I put them on my own website for people to grab and test, or do a normal upload? -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: python 2.6 in GUB Re: LilyPond-Book on Windows
Doesn't Julien have GUB with python 2.6 ready for testing? I If I install lilypond on my Fedora 20 system using the version from the official Fedora repo (2.18.2) it will use the Python2 version that is shipped with Fedora (Python 2.7.5) and I never experienced problems with that. The installers from the Lilypond website are shipped with an older Python version. Are there any known issues that I - as a normal user - might encounter (but haven't encountered yet) when using the Fedora distributed Lilypond and Python versions? -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: python 2.6 in GUB Re: LilyPond-Book on Windows
On Sun, Apr 06, 2014 at 10:44:19AM +0100, Phil Holmes wrote: Doesn't Julien have GUB with python 2.6 ready for testing? I should be able to test GUB with Julien's Python 2.6 later this week. I'd just like to check the process. I click the Merge pull request at https://github.com/gperciva/gub/pull/6 and this pushes Julien's changes into the GUB repo? I do not recommend this -- his changes are untested, so we don't want that to become master on the (I think?) official GUB used for lilypond. (incidently, I second the calls to have a shared lilypond account on github. I understand David's concerns about github, and realize that moving to savannah might be better in the long term. But in the short term, going from github:gperciva to github:lilypond does not lose anything. And it's been months and months (maybe over a year?) since I left lilypond development) I then pull the GUB repo on my GUB VM and this will get the changes into my version of GUB? There's a way to get Julien's changes onto your local computer to test them, but I can't speak with any certainty as to how this is done. I then make lilypond as usual. What if it doesn't work? We then need to test the built binaries: should I put them on my own website for people to grab and test, or do a normal upload? Please put them on your own website for people to grab and test. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: python 2.6 in GUB Re: LilyPond-Book on Windows
There _is_ a lilypond organization on github already, created and owned by Janek. We can easily fork the necessary repositories there and give all persons the necessary push access. As to the merge question: As Graham sais you shouldn't merge the request. Rather add the respective fork as a remote to your local clone and pull the interesting branches there. Then test and merge manually. Urs Graham Percival gra...@percival-music.ca schrieb am 06.04.2014: On Sun, Apr 06, 2014 at 10:44:19AM +0100, Phil Holmes wrote: Doesn't Julien have GUB with python 2.6 ready for testing? I should be able to test GUB with Julien's Python 2.6 later this week. I'd just like to check the process. I click the Merge pull request at https://github.com/gperciva/gub/pull/6 and this pushes Julien's changes into the GUB repo? I do not recommend this -- his changes are untested, so we don't want that to become master on the (I think?) official GUB used for lilypond. (incidently, I second the calls to have a shared lilypond account on github. I understand David's concerns about github, and realize that moving to savannah might be better in the long term. But in the short term, going from github:gperciva to github:lilypond does not lose anything. And it's been months and months (maybe over a year?) since I left lilypond development) I then pull the GUB repo on my GUB VM and this will get the changes into my version of GUB? There's a way to get Julien's changes onto your local computer to test them, but I can't speak with any certainty as to how this is done. I then make lilypond as usual. What if it doesn't work? We then need to test the built binaries: should I put them on my own website for people to grab and test, or do a normal upload? Please put them on your own website for people to grab and test. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- Diese Nachricht wurde mit a href=https://play.google.com/store/apps/details?id=com.onegravity.k10.pro2;bK-@ Mail/b/a gesendet.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
David Kastrup writes: So my first impulse would be to throw out the workaround for 2.4.2 that Let's do that. Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Jan Nieuwenhuizen jann...@gnu.org writes: David Kastrup writes: So my first impulse would be to throw out the workaround for 2.4.2 that Let's do that. Well, issue 1933 URL:http://code.google.com/p/lilypond/issues/detail?id=1933 would suggest that this is a bad idea. Nothing substantially has changed since then. I'm currently trying to get the TEXINPUTS stuff integrated into the Mingw fix to arrive back at a working lilypond-book, but of course it is to be hoped that moving Python forward to 2.6 might make that problem go away. But it will take longer to figure that out. Our current 2.4.5 Python aborts with an error traceback even when doing exit(0) which is sort of ridiculous. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
python 2.6 in GUB Re: LilyPond-Book on Windows
On Sat, Apr 05, 2014 at 08:53:04AM +0200, David Kastrup wrote: Jan Nieuwenhuizen jann...@gnu.org writes: David Kastrup writes: So my first impulse would be to throw out the workaround for 2.4.2 that Let's do that. Well, issue 1933 URL:http://code.google.com/p/lilypond/issues/detail?id=1933 would suggest that this is a bad idea. Nothing substantially has changed since then. I'm currently trying to get the TEXINPUTS stuff integrated into the Mingw fix to arrive back at a working lilypond-book, but of course it is to be hoped that moving Python forward to 2.6 might make that problem go away. But it will take longer to figure that out. Doesn't Julien have GUB with python 2.6 ready for testing? I would move forward on that before diving into the dark waters of os.popen in python 2.4. I remember bug 1933; it was really annoying. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Br. Samuel Springuel rpspring...@gmail.com writes:
Perhaps I wasn't clear, but I did not include a test document because
I get the fault no matter what. I've even tested a document which was
devoid of content and consisted of exactly 5 commands:
\documentclass{article}
\begin{document}
\begin{lilypond}
\end{lilypond}
\end{document}
The same fault occurs. Further, documents which work just fine on a
Mac and on Linux fail to work on Windows. The only difference is the
OS. Something appears to be wrong with the way lilypond-book operates
in Windows.
Since you were actually previously talking about MacOSX, the same fault
occurs is totally useless. You now talk about Windows. You don't
mention your version of Windows. You don't mention your version of
LilyPond. You don't mention the problem that occurs.
You do not even reply to the same thread as the previous discussion but
create a new thread, making it harder to find information which you
assume everybody should remember but which actually is not all that
helpful for diagnosing a _Windows_ problem since you were previously
talking about MacOSX.
Do you really expect people to do all the detective and guess work
trying to figure out what you are doing on which platform with which
versions and what goes wrong with it?
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
The list or its Gmane mirror seems sort of messed up. I think I answered something further down in the line already. Br. Samuel Springuel rpspring...@gmail.com writes: I'm having trouble using lilypond-book on my Windows machine. The program sees to hang during the initial run of the typesetting engine that's used to determine the page settings. In this case, by hang I mean that everything proceeds normally up to this point, but then nothing happens, even if left for several hours, until I eventually use a KeyboardInterrupt to arrest the process. This happens with two different typesetting engines (lualatex and pdflatex), both of which work on other documents. This leads me to suspect that there's a problem in lilypond-book itself. Any ideas as to what the problem might be? lilypond-book.py (GNU LilyPond) 2.18.2 Reading Advent-Christmas.lytex... Running `lualatex --shell-escape' on file `c:\docume~1\admin\locals~1\temp\tmpgz qsfb.tex' to detect default page settings. Executing: lualatex --shell-escape c:\docume~1\admin\locals~1\temp\tmpgzqsfb.tex Sigh. I suspect ### unknown why this is necessary universal_newlines = True if sys.platform == 'mingw32': universal_newlines = False if (sys.platform == 'mingw32') and (sys.version_info (2, 6)): ### use os.system to avoid weird sleep() problems on ### GUB's python 2.4.2 on mingw # make file to write to output_dir = tempfile.mkdtemp() output_filename = os.path.join(output_dir, 'output.txt') # call command cmd += %s % output_filename returncode = os.system(cmd) parameter_string = open(output_filename).read() if returncode != 0: warning (_ (Unable to auto-detect default settings:\n)) # clean up os.remove(output_filename) os.rmdir(output_dir) else: proc = subprocess.Popen (cmd, env=run_env, universal_newlines=universal_newlines, shell=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE) (parameter_string, error_string) = proc.communicate () if proc.returncode != 0: warning (_ (Unable to auto-detect default settings:\n%s) % error_string) os.unlink (tmpfile) in python/book_latex.py here. This will be due to one of commit aa89d7b8d687e42cdbf11b14dc8e0b4827a8aa9e Author: David Kastrup d...@gnu.org Date: Sat Feb 22 20:54:11 2014 +0100 Issue 3874: lilypond-book: Fix TEXINPUTS environment manipulation on W32 commit 1f2bdee043a85ddca79be8ef99b206fb3a97b289 Author: David Kastrup d...@gnu.org Date: Sat Feb 22 20:53:34 2014 +0100 Restrict lilypond-book mingw32 subprocess workaround to Python versions 2.6 If we had somewhat more reliable feedback from Windows users (this was already released in 2.19.3, see URL:https://lists.gnu.org/archive/html/bug-lilypond/2014-03/msg00063.html), then the quality of our releases could be better. It would appear that the above code using subprocess.Popen will most likely make lilypond-book hang on Windows for essentially unknown reasons. Any idea what your Python version is? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
- Original Message - From: David Kastrup d...@gnu.org To: Br. Samuel Springuel rpspring...@gmail.com Cc: lilypond-user@gnu.org Sent: Thursday, April 03, 2014 1:44 PM Subject: Re: LilyPond-Book on Windows If we had somewhat more reliable feedback from Windows users (this was already released in 2.19.3, see URL:https://lists.gnu.org/archive/html/bug-lilypond/2014-03/msg00063.html), then the quality of our releases could be better. I suspect that most windows users aren't using lilypond-book: partly because of the need to use other Unix-like programs to convert the TeX. I certainly don't, and if I had a need to use lilypond-book, I'd do it in a Unix VM. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: Br. Samuel Springuel rpspring...@gmail.com Cc: lilypond-user@gnu.org Sent: Thursday, April 03, 2014 1:44 PM Subject: Re: LilyPond-Book on Windows If we had somewhat more reliable feedback from Windows users (this was already released in 2.19.3, see URL:https://lists.gnu.org/archive/html/bug-lilypond/2014-03/msg00063.html), then the quality of our releases could be better. I suspect that most windows users aren't using lilypond-book: partly because of the need to use other Unix-like programs to convert the TeX. I certainly don't, and if I had a need to use lilypond-book, I'd do it in a Unix VM. It's not just that: most Windows users aren't actively participating on the lists, either. I have asked several times on one of the lists what the result of exit(0) inside of the Python we deliver with Windows (?) would be. Should not be too hard, but no response. It's not clear to me what version of Python we actually deliver (and I was apparently pointed to the wrong GUB repository for finding that out the hard way by looking at the source). So it would appear that we still deliver a broken version of LilyPond-book in 2.18.2 since no Windows users are interested in it enough that we would have gotten a report about it in the month that it was available in the developer releases. At the current rate, it will take half a year or longer before we get this fixed. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
- Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: Br. Samuel Springuel rpspring...@gmail.com; lilypond-user@gnu.org Sent: Thursday, April 03, 2014 2:07 PM Subject: Re: LilyPond-Book on Windows Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: Br. Samuel Springuel rpspring...@gmail.com Cc: lilypond-user@gnu.org Sent: Thursday, April 03, 2014 1:44 PM Subject: Re: LilyPond-Book on Windows If we had somewhat more reliable feedback from Windows users (this was already released in 2.19.3, see URL:https://lists.gnu.org/archive/html/bug-lilypond/2014-03/msg00063.html), then the quality of our releases could be better. I suspect that most windows users aren't using lilypond-book: partly because of the need to use other Unix-like programs to convert the TeX. I certainly don't, and if I had a need to use lilypond-book, I'd do it in a Unix VM. It's not just that: most Windows users aren't actively participating on the lists, either. I have asked several times on one of the lists what the result of exit(0) inside of the Python we deliver with Windows (?) would be. Should not be too hard, but no response. It's not clear to me what version of Python we actually deliver (and I was apparently pointed to the wrong GUB repository for finding that out the hard way by looking at the source). Sorry - probably busy with other stuff. This may be what you want: C:\Program Files (x86)\LilyPondV2.18.0\usr\binpython Python 2.4.5 (#1, Oct 6 2013, 18:41:07) [GCC 4.1.1] on mingw32 Type help, copyright, credits or license for more information. exit(0) Traceback (most recent call last): File stdin, line 1, in ? TypeError: 'str' object is not callable -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: Br. Samuel Springuel rpspring...@gmail.com; lilypond-user@gnu.org Sent: Thursday, April 03, 2014 2:07 PM Subject: Re: LilyPond-Book on Windows It's not just that: most Windows users aren't actively participating on the lists, either. I have asked several times on one of the lists what the result of exit(0) inside of the Python we deliver with Windows (?) would be. Should not be too hard, but no response. It's not clear to me what version of Python we actually deliver (and I was apparently pointed to the wrong GUB repository for finding that out the hard way by looking at the source). Sorry - probably busy with other stuff. This may be what you want: C:\Program Files (x86)\LilyPondV2.18.0\usr\binpython Python 2.4.5 (#1, Oct 6 2013, 18:41:07) [GCC 4.1.1] on mingw32 Type help, copyright, credits or license for more information. exit(0) Traceback (most recent call last): File stdin, line 1, in ? TypeError: 'str' object is not callable What I suspected. Like the problem that gets a workaround in LilyPond-book (and I am afraid that the workaround will likely break the TEXINPUTS manipulation and thus does not lead to a working program), this is pretty absurd. Instead of trying to find something nicer, like os.exit or sys.exit or whatever, I think it would make more sense first to move to version 2.6 (which probably means updating to Jan's repository and/or merging it into Graham's) and see how we fare there. It's quite conceivable that blunders like that are fixed in later versions. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
- Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: Br. Samuel Springuel rpspring...@gmail.com; lilypond-user@gnu.org Sent: Thursday, April 03, 2014 2:36 PM Subject: Re: LilyPond-Book on Windows Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: Br. Samuel Springuel rpspring...@gmail.com; lilypond-user@gnu.org Sent: Thursday, April 03, 2014 2:07 PM Subject: Re: LilyPond-Book on Windows It's not just that: most Windows users aren't actively participating on the lists, either. I have asked several times on one of the lists what the result of exit(0) inside of the Python we deliver with Windows (?) would be. Should not be too hard, but no response. It's not clear to me what version of Python we actually deliver (and I was apparently pointed to the wrong GUB repository for finding that out the hard way by looking at the source). Sorry - probably busy with other stuff. This may be what you want: C:\Program Files (x86)\LilyPondV2.18.0\usr\binpython Python 2.4.5 (#1, Oct 6 2013, 18:41:07) [GCC 4.1.1] on mingw32 Type help, copyright, credits or license for more information. exit(0) Traceback (most recent call last): File stdin, line 1, in ? TypeError: 'str' object is not callable What I suspected. Like the problem that gets a workaround in LilyPond-book (and I am afraid that the workaround will likely break the TEXINPUTS manipulation and thus does not lead to a working program), this is pretty absurd. Instead of trying to find something nicer, like os.exit or sys.exit or whatever, I think it would make more sense first to move to version 2.6 (which probably means updating to Jan's repository and/or merging it into Graham's) and see how we fare there. It's quite conceivable that blunders like that are fixed in later versions. -- David Kastrup It would only need Graham's repo to be updated: I pull from there. For any updates to Gub or -extra, only Graham's repo is used. However, I have no idea how the update would be performed. Might be worth asking if there's a windows user with a later version of Python that could try exit(0). -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Phil Holmes m...@philholmes.net writes: Sorry - probably busy with other stuff. This may be what you want: C:\Program Files (x86)\LilyPondV2.18.0\usr\binpython Python 2.4.5 (#1, Oct 6 2013, 18:41:07) [GCC 4.1.1] on mingw32 Type help, copyright, credits or license for more information. exit(0) Traceback (most recent call last): File stdin, line 1, in ? TypeError: 'str' object is not callable What I suspected. Like the problem that gets a workaround in LilyPond-book (and I am afraid that the workaround will likely break the TEXINPUTS manipulation and thus does not lead to a working program), this is pretty absurd. Instead of trying to find something nicer, like os.exit or sys.exit or whatever, I think it would make more sense first to move to version 2.6 (which probably means updating to Jan's repository and/or merging it into Graham's) and see how we fare there. It's quite conceivable that blunders like that are fixed in later versions. It would only need Graham's repo to be updated: I pull from there. For any updates to Gub or -extra, only Graham's repo is used. However, I have no idea how the update would be performed. Might be worth asking if there's a windows user with a later version of Python that could try exit(0). The exit thing is more like a nuisance: it leads to misleading error messages after an actual error is diagnosed. The other thing is more critical. It may very well be that only our GUB-bootstrapped binaries are affected. Now if our current distributed version is 2.4.5, we'll still get into the path if (sys.platform == 'mingw32') and (sys.version_info (2, 6)): ### use os.system to avoid weird sleep() problems on ### GUB's python 2.4.2 on mingw So my first impulse would be to throw out the workaround for 2.4.2 that has ceased to work out once we are meddling with TEXINPUTS and see what happens. However, it is a reasonable suspicion that we'll get back whatever behavior led to the workaround to get introduced in the first place. The workaround is not all that old: commit ab8dfc6e8f3de3cefc8fab09a4993acaec460720 Author: Graham Percival gra...@percival-music.ca Date: Thu Jan 12 05:57:59 2012 + lilypond-book: avoid subprocess for mingw And the corresponding issue is URL:http://code.google.com/p/lilypond/issues/detail?id=1933 So I have no idea what to do here. The mentioned subprocess commit is in Graham's repository URL:https://github.com/gperciva/gub/commit/e3d46689d881045ceb2dbf31d7d4573709f781d8 so the occurence of issue 1933 would suggest that this workaround can't really be omitted for version 2.4.5. Copying Graham and Jan in case they have some suggestion here. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
On 03/04/2014 9:48 AM, Phil Holmes wrote: - Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: Br. Samuel Springuel rpspring...@gmail.com; lilypond-user@gnu.org Sent: Thursday, April 03, 2014 2:36 PM Subject: Re: LilyPond-Book on Windows Instead of trying to find something nicer, like os.exit or sys.exit or whatever, I think it would make more sense first to move to version 2.6 (which probably means updating to Jan's repository and/or merging it into Graham's) and see how we fare there. It's quite conceivable that blunders like that are fixed in later versions. It would only need Graham's repo to be updated: I pull from there. For any updates to Gub or -extra, only Graham's repo is used. However, I have no idea how the update would be performed. Clicking Merge pull request here for a start: https://github.com/gperciva/gub/pull/6 -- Julien ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
David wrote Thursday, April 03, 2014 2:07 PM So it would appear that we still deliver a broken version of LilyPond-book in 2.18.2 since no Windows users are interested in it enough that we would have gotten a report about it in the month that it was available in the developer releases. I use lilypond-book under Windows, but only for compiling sections of the documentation. It works fine for me, even 2.19.3. I don't use Latex at all. Well, by fine I mean it does what I need. The opening preamble which attempts to determine some line width fails, but it has failed in the same way for ages, since Graham's workaround for the problem David mentions - 1933. Running lilypond-book lilypond-book.py (GNU LilyPond) 2.19.3 Reading C:/Users/Trevor/LilyPond-git/Documentation/contributor/doc-work.itexi... Running texi2pdf on file c:\users\trevor\appdata\local\temp\tmpuyivbf.texi to detect default page settings. 'texi2pdf' is not recognized as an internal or external command, operable program or batch file. lilypond-book.py: warning: Unable to auto-detect default settings: Dissecting... Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Trevor Daniels t.dani...@treda.co.uk writes: David wrote Thursday, April 03, 2014 2:07 PM So it would appear that we still deliver a broken version of LilyPond-book in 2.18.2 since no Windows users are interested in it enough that we would have gotten a report about it in the month that it was available in the developer releases. I use lilypond-book under Windows, but only for compiling sections of the documentation. It works fine for me, even 2.19.3. I don't use Latex at all. The latest problems are in the LaTeX part and the problematic functionality involving TEXINPUTS has not apparently been ported to Texinfo. Well, by fine I mean it does what I need. The opening preamble which attempts to determine some line width fails, but it has failed in the same way for ages, since Graham's workaround for the problem David mentions - 1933. Just fabulous. So we have been using a fix that causes reliable failure since 2.16. Running lilypond-book lilypond-book.py (GNU LilyPond) 2.19.3 Reading C:/Users/Trevor/LilyPond-git/Documentation/contributor/doc-work.itexi... Running texi2pdf on file c:\users\trevor\appdata\local\temp\tmpuyivbf.texi to detect default page settings. 'texi2pdf' is not recognized as an internal or external command, operable program or batch file. That looks like a path problem. lilypond-book.py: warning: Unable to auto-detect default settings: -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
- Original Message - From: David Kastrup d...@gnu.org To: Trevor Daniels t.dani...@treda.co.uk Cc: Phil Holmes m...@philholmes.net; lilypond-user@gnu.org Sent: Thursday, April 03, 2014 4:14 PM Subject: Re: LilyPond-Book on Windows Trevor Daniels t.dani...@treda.co.uk writes: David wrote Thursday, April 03, 2014 2:07 PM So it would appear that we still deliver a broken version of LilyPond-book in 2.18.2 since no Windows users are interested in it enough that we would have gotten a report about it in the month that it was available in the developer releases. I use lilypond-book under Windows, but only for compiling sections of the documentation. It works fine for me, even 2.19.3. I don't use Latex at all. The latest problems are in the LaTeX part and the problematic functionality involving TEXINPUTS has not apparently been ported to Texinfo. Well, by fine I mean it does what I need. The opening preamble which attempts to determine some line width fails, but it has failed in the same way for ages, since Graham's workaround for the problem David mentions - 1933. Just fabulous. So we have been using a fix that causes reliable failure since 2.16. As I said many times on the notes of 1933, the line width detection was put in solely to avoid the black bars we used to get in our documentation: it had no other purpose. Given that nobody compiles the final documents on windows, the fact that it fails is of no relevance whatever. -- David Kastrup -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: Trevor Daniels t.dani...@treda.co.uk Cc: Phil Holmes m...@philholmes.net; lilypond-user@gnu.org Sent: Thursday, April 03, 2014 4:14 PM Subject: Re: LilyPond-Book on Windows Trevor Daniels t.dani...@treda.co.uk writes: David wrote Thursday, April 03, 2014 2:07 PM So it would appear that we still deliver a broken version of LilyPond-book in 2.18.2 since no Windows users are interested in it enough that we would have gotten a report about it in the month that it was available in the developer releases. I use lilypond-book under Windows, but only for compiling sections of the documentation. It works fine for me, even 2.19.3. I don't use Latex at all. The latest problems are in the LaTeX part and the problematic functionality involving TEXINPUTS has not apparently been ported to Texinfo. Well, by fine I mean it does what I need. The opening preamble which attempts to determine some line width fails, but it has failed in the same way for ages, since Graham's workaround for the problem David mentions - 1933. Just fabulous. So we have been using a fix that causes reliable failure since 2.16. As I said many times on the notes of 1933, the line width detection was put in solely to avoid the black bars we used to get in our documentation: it had no other purpose. Given that nobody compiles the final documents on windows, the fact that it fails is of no relevance whatever. Except for Windows users of lilypond-book. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
- Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: Trevor Daniels t.dani...@treda.co.uk; lilypond-user@gnu.org Sent: Thursday, April 03, 2014 4:34 PM Subject: Re: LilyPond-Book on Windows Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: Trevor Daniels t.dani...@treda.co.uk Cc: Phil Holmes m...@philholmes.net; lilypond-user@gnu.org Sent: Thursday, April 03, 2014 4:14 PM Subject: Re: LilyPond-Book on Windows Trevor Daniels t.dani...@treda.co.uk writes: David wrote Thursday, April 03, 2014 2:07 PM So it would appear that we still deliver a broken version of LilyPond-book in 2.18.2 since no Windows users are interested in it enough that we would have gotten a report about it in the month that it was available in the developer releases. I use lilypond-book under Windows, but only for compiling sections of the documentation. It works fine for me, even 2.19.3. I don't use Latex at all. The latest problems are in the LaTeX part and the problematic functionality involving TEXINPUTS has not apparently been ported to Texinfo. Well, by fine I mean it does what I need. The opening preamble which attempts to determine some line width fails, but it has failed in the same way for ages, since Graham's workaround for the problem David mentions - 1933. Just fabulous. So we have been using a fix that causes reliable failure since 2.16. As I said many times on the notes of 1933, the line width detection was put in solely to avoid the black bars we used to get in our documentation: it had no other purpose. Given that nobody compiles the final documents on windows, the fact that it fails is of no relevance whatever. Except for Windows users of lilypond-book. -- David Kastrup Did you read what I wrote? It's _only_ relevant for compiling the LilyPond docs: lilypond-book users do not need automatic line-width detection. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Phil Holmes m...@philholmes.net writes: As I said many times on the notes of 1933, the line width detection was put in solely to avoid the black bars we used to get in our documentation: it had no other purpose. Given that nobody compiles the final documents on windows, the fact that it fails is of no relevance whatever. Except for Windows users of lilypond-book. Did you read what I wrote? It's _only_ relevant for compiling the LilyPond docs: lilypond-book users do not need automatic line-width detection. Why wouldn't they? The black bars are produced by Texinfo in draft mode for overfull lines. But just because other setups do not produce black boxes for overfull lines by default does not mean that a mismatch of score systems and text linewidth is desirable. Nor is a difference in output on Windows and other systems desirable. It makes stuff irreproducible. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
David Kastrup Thursday, April 03, 2014 4:14 PM Trevor Daniels t.dani...@treda.co.uk writes: 'texi2pdf' is not recognized as an internal or external command, operable program or batch file. That looks like a path problem. No, it's because I couldn't find a version of texi2pdf that works under Windows, so I don't have such a program installed. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
David Kastrup Thursday, April 03, 2014 4:14 PM Trevor Daniels t.dani...@treda.co.uk writes: 'texi2pdf' is not recognized as an internal or external command, operable program or batch file. That looks like a path problem. No, it's because I couldn't find a version of texi2pdf that works under Windows, so I don't have such a program installed. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Sorry if this is a double, but I hit the wrong reply button on the first one. On 2014-04-03 8:44 AM, David Kastrup wrote: It would appear that the above code using subprocess.Popen will most likely make lilypond-book hang on Windows for essentially unknown reasons. Any idea what your Python version is? The conversation seems to have moved beyond this, but LilyPond delivered Python 2.4.5 on my machine. Basic System information (sorry for forgetting this): The Windows machine is running Windows XP SP3, and LilyPond 2.18.2. The Mac (which is only used in the case of this problem to test and make sure that I have well formed documents) runs OS 10.8.5 and LilyPond 2.18.2-1. I also have Python 3.3.4 installed separately on the Windows machine and used to have some variety of Python 2.7 which I had removed before I installed LilyPond because I was no longer using it in my Windows environment (I do most of my programing on my Mac now). I could put that back if it would be useful. ✝ Br. Samuel (R. Padraic Springuel) PAX ☧ ΧΡΙΣΤΟΣ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Trevor Daniels t.dani...@treda.co.uk writes: David Kastrup Thursday, April 03, 2014 4:14 PM Trevor Daniels t.dani...@treda.co.uk writes: 'texi2pdf' is not recognized as an internal or external command, operable program or batch file. That looks like a path problem. No, it's because I couldn't find a version of texi2pdf that works under Windows, so I don't have such a program installed. Well, you wrote: I use lilypond-book under Windows, but only for compiling sections of the documentation. It works fine for me, even 2.19.3. I don't use Latex at all. Now if you use lilypond-book successfully under Windows for compiling sections of the documentation, then obviously _some_ command is used for generating some output. If that program isn't texi2pdf, then that's what we should be using for linewidth detection as well. Or at least something that gets us as close as possible. Can you actually produce a PDF in some manner? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
David, you wrote Thursday, April 03, 2014 6:40 PM Well, you wrote: I use lilypond-book under Windows, but only for compiling sections of the documentation. It works fine for me, even 2.19.3. I don't use Latex at all. Now if you use lilypond-book successfully under Windows for compiling sections of the documentation, then obviously _some_ command is used for generating some output. If that program isn't texi2pdf, then that's what we should be using for linewidth detection as well. Or at least something that gets us as close as possible. Can you actually produce a PDF in some manner? No. I use texi2html, which does work under windows. It's quite adequate for me to check that the section of the docs compiles with my changes, and to give me an idea of the effect of any formatting. It's the way I've done all my doc work, which amounts to getting on for half the NR and rather more than half the LM. AFAIK html doesn't have the concept of linewidth. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
On Wed, Apr 02, 2014 at 08:58:52AM -0400, Br. Samuel Springuel wrote: I'm having trouble using lilypond-book on my Windows machine. The program sees to hang during the initial run of the typesetting engine that's used to determine the page settings. In this case, by hang I mean that everything proceeds normally up to this point, but then nothing happens, even if left for several hours, until I eventually use a KeyboardInterrupt to arrest the process. This happens with two different typesetting engines (lualatex and pdflatex), both of which work on other documents. This leads me to suspect that there's a problem in lilypond-book itself. Any ideas as to what the problem might be? I'm afraid I'm not likely to be of help, since I don't use either of those products, but this is where a tiny example is your best friend. By making a copy of your input file and condensing to the bare minimum needed to produce the fault, you'll either find the problem in the input file, or have a concrete example to share with the list. Jim ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-Book on Windows
Perhaps I wasn't clear, but I did not include a test document because I
get the fault no matter what. I've even tested a document which was
devoid of content and consisted of exactly 5 commands:
\documentclass{article}
\begin{document}
\begin{lilypond}
\end{lilypond}
\end{document}
The same fault occurs. Further, documents which work just fine on a Mac
and on Linux fail to work on Windows. The only difference is the OS.
Something appears to be wrong with the way lilypond-book operates in
Windows.
✝
Br. Samuel
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond-book on Windows 2.16.1
- Original Message - From: Julien Rioux jri...@lyx.org To: lilypond-user@gnu.org Sent: Friday, January 04, 2013 9:43 PM Subject: Re: Lilypond-book on Windows 2.16.1 On 04/01/2013 4:30 PM, Phil Holmes wrote: Thanks for testing this. 2.16.2 is currently uploading and the stable build (which you have actually already downloaded from my website) should be on lilypond.org tomorrow. -- Phil Holmes Thanks for tackling this, Phil, and thanks to those who ran tests. BTW, should the backported patches be marked fixed_2_16_2 on the issue tracker, as David did for 2_16_x before? Done. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond-book on Windows 2.16.1
On 01/04/2013 06:00 PM, lilypond-user-requ...@gnu.org wrote: I have created a new stable version of the windows binary (2.16.2) which should fix the problem that prevents lilypond-book from being run on 2.16.1. Before uploading this to the official website, I would appreciate it if interested and capable users could download it from my own website: http://philholmes.net/lilypond/lilypond-2.16.2-1.mingw.exe and test the lilypond-book functionality. Please reply-all with your results. I would appreciate it if those interested in a fix could do this as soon as possible. Works like a charm on Win7 professional. Note that my last previous install was 2.16.0 which also worked well, so I haven't tested an update from 2.16.1. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond-book on Windows 2.16.1
On Fri, Jan 4, 2013 at 4:12 PM, Phil Holmes em...@philholmes.net wrote: I have created a new stable version of the windows binary (2.16.2) which should fix the problem that prevents lilypond-book from being run on 2.16.1. Before uploading this to the official website, I would appreciate it if interested and capable users could download it from my own website: http://philholmes.net/**lilypond/lilypond-2.16.2-1.**mingw.exehttp://philholmes.net/lilypond/lilypond-2.16.2-1.mingw.exe and test the lilypond-book functionality. Please reply-all with your results. I would appreciate it if those interested in a fix could do this as soon as possible. Dear Phil, I tested on Win7 x64, uninstalled LilyPond 2.16.1 and installed LilyPond 2.16.2. LilyPond works, as does lilypond-book.py now. No longer do I need to run python on the .py file as I reported earlier with LilyPond 2.16.1. I already updated my makefile to reflect the fix in LilyPond 2.16.2. Best regards and many thanks! Olivier ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond-book on Windows 2.16.1
Thanks for testing this. 2.16.2 is currently uploading and the stable build (which you have actually already downloaded from my website) should be on lilypond.org tomorrow. -- Phil Holmes - Original Message - From: Olivier Biot To: Phil Holmes Cc: Chris ; Per Sennels ; LilyPond User Group Sent: Friday, January 04, 2013 9:23 PM Subject: Re: Lilypond-book on Windows 2.16.1 On Fri, Jan 4, 2013 at 4:12 PM, Phil Holmes em...@philholmes.net wrote: I have created a new stable version of the windows binary (2.16.2) which should fix the problem that prevents lilypond-book from being run on 2.16.1. Before uploading this to the official website, I would appreciate it if interested and capable users could download it from my own website: http://philholmes.net/lilypond/lilypond-2.16.2-1.mingw.exe and test the lilypond-book functionality. Please reply-all with your results. I would appreciate it if those interested in a fix could do this as soon as possible. Dear Phil, I tested on Win7 x64, uninstalled LilyPond 2.16.1 and installed LilyPond 2.16.2. LilyPond works, as does lilypond-book.py now. No longer do I need to run python on the .py file as I reported earlier with LilyPond 2.16.1. I already updated my makefile to reflect the fix in LilyPond 2.16.2. Best regards and many thanks! Olivier -- ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond-book on Windows 2.16.1
On 04/01/2013 4:30 PM, Phil Holmes wrote: Thanks for testing this. 2.16.2 is currently uploading and the stable build (which you have actually already downloaded from my website) should be on lilypond.org tomorrow. -- Phil Holmes Thanks for tackling this, Phil, and thanks to those who ran tests. BTW, should the backported patches be marked fixed_2_16_2 on the issue tracker, as David did for 2_16_x before? -- Julien ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond-book on Windows 2.16.1
Hi Phil et al, downloaded, installed and tested, with both normal lilypond and lilypond-book, without any problems. Thanks for fixing this problem so quickly, Best Per Sennels 2013/1/4 Phil Holmes em...@philholmes.net I have created a new stable version of the windows binary (2.16.2) which should fix the problem that prevents lilypond-book from being run on 2.16.1. Before uploading this to the official website, I would appreciate it if interested and capable users could download it from my own website: http://philholmes.net/**lilypond/lilypond-2.16.2-1.**mingw.exehttp://philholmes.net/lilypond/lilypond-2.16.2-1.mingw.exe and test the lilypond-book functionality. Please reply-all with your results. I would appreciate it if those interested in a fix could do this as soon as possible. Thanks. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond-book on Windows 2.16.1
Julien Rioux jri...@lyx.org writes: On 04/01/2013 4:30 PM, Phil Holmes wrote: Thanks for testing this. 2.16.2 is currently uploading and the stable build (which you have actually already downloaded from my website) should be on lilypond.org tomorrow. -- Phil Holmes Thanks for tackling this, Phil, and thanks to those who ran tests. BTW, should the backported patches be marked fixed_2_16_2 on the issue tracker, as David did for 2_16_x before? I should think so. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
