Re: Yet another 2 patches for music streams
On Tuesday 23 May 2006 13:01, Han-Wen Nienhuys wrote:
> *Please commit the 1st patch after lyricsto works again.
I have committed now. There are two problems still, whihc I ignored (they do
not affect make web):
- input/no-notation/denneboom.ly uses \oldaddlyrics. However, it didn't work
before my patch either, so I guess the file is obsolete anyways
- input/no-notation/display-lily-tests.ly also contains an oldaddlyrics
reference, but lily fails on the file anyway.
Graham, I have changed the syntax of \applyOutput; instead of \context Staff
\applyOutput {..} you should now write \applyoutput #'Staff {..} . The manual
might be affected by this change.
--
Erik
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: maze of documentation GNUmakefiles
Graham Percival schreef: but it still used the normal texinfo rules (with no -E). How can I have two different texi2dvi commands? I've trawled around in buildscripts/lys-to-texi.py (trying to make input/* work with -E), GNUmakefiles, stepmake/stepmake/texinfo-*.make, and I'm now totally lost and disheartened. This was supposed to be a one-hour documentation job and has turned into ten hours of immense frustration dealing with various low-level things. I'm supposed to be grammar-checking English and pretending to be a newbie (to write docs for them) ! Welcome to the world of Open Source maintenance! You're now officially One Of Us. I've added a TEXI2DVI_FLAGS option to texinfo-rules.make -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Yet another 2 patches for music streams
Erik Sandberg schreef: On Tuesday 23 May 2006 13:01, Han-Wen Nienhuys wrote: *Please commit the 1st patch after lyricsto works again. I have committed now. There are two problems still, whihc I ignored (they do not affect make web): - input/no-notation/denneboom.ly uses \oldaddlyrics. However, it didn't work before my patch either, so I guess the file is obsolete anyways yes, removed. - input/no-notation/display-lily-tests.ly also contains an oldaddlyrics reference, but lily fails on the file anyway. Hmm. Nicolas? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: maze of documentation GNUmakefiles
> input/* requires texi2dvi without the -E. This should never happen. I consider such a situation as a bug, and you should report it to the texinfo people. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Yet another 2 patches for music streams
Erik Sandberg schreef:
On Tuesday 23 May 2006 13:01, Han-Wen Nienhuys wrote:
*Please commit the 1st patch after lyricsto works again.
I have committed now. There are two problems still, whihc I ignored (they do
not affect make web):
- input/no-notation/denneboom.ly uses \oldaddlyrics. However, it didn't work
before my patch either, so I guess the file is obsolete anyways
- input/no-notation/display-lily-tests.ly also contains an oldaddlyrics
reference, but lily fails on the file anyway.
Graham, I have changed the syntax of \applyOutput; instead of \context Staff
\applyOutput {..} you should now write \applyoutput #'Staff {..} . The manual
might be affected by this change.
Erik,
I asked you to check "make web". The manual is part of that, now it
barfs with
/Users/lilytest/testing/gub/target/darwin-ppc/build/lilypond-HEAD/Documentation/user/out-www/lily-1173155923.ly:70:3:
error: syntax error, unexpected '<'
/Users/lilytest/testing/gub/target/darwin-ppc/build/lilypond-HEAD/Documentation/user/out-www/lily-1173155923.ly:73:50:
error: syntax error, unexpected RESTNAME
\repeat unfold 5 { \applyOutput #mc-squared
s8 }
Can you actually check "make web-clean ; make web", even for the tiniest
change that you commit?
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
out/bin/*.ly ?
What is the meaning of *.ly which point to nothing below ? $ ls -l out/bin/ total 0 lrwxrwxrwx 1 karl users 22 May 22 17:57 *.ly -> ../../scripts/out/*.ly lrwxrwxrwx 1 karl users 28 May 22 17:57 convert-ly -> ../../scripts/out/convert-ly lrwxrwxrwx 1 karl users 23 May 22 17:57 lilypond -> ../../lily/out/lilypond lrwxrwxrwx 1 karl users 31 May 22 17:57 lilypond-book -> ../../scripts/out/lilypond-book $ Maybe it should read ln -s .../*2ly . instead of *.ly ? If so, use attached patch. Also note that target $(tree-share-prefix)/lilypond-force in toplevel GNUmakefile is run before the generation of the files in scripts/out/ so any wildcard are useless in the line above, and will generate the file *.ly instead of expanding to future files. * GNUmakefile.in: wildcard in ln -s .../*.ly . don't work when newly checkout'ed Regards, /Karl Index: GNUmakefile.in === RCS file: /sources/lilypond/lilypond/GNUmakefile.in,v retrieving revision 1.188 diff -u -r1.188 GNUmakefile.in --- GNUmakefile.in 25 Feb 2006 00:20:51 - 1.188 +++ GNUmakefile.in 24 May 2006 12:09:13 - @@ -132,9 +132,8 @@ mkdir -p $(tree-share-prefix)/tex cd $(tree-bin) && \ ln -sf ../../lily/$(outconfbase)/lilypond . && \ - ln -sf ../../scripts/$(outconfbase)/convert-ly . && \ - ln -sf ../../scripts/$(outconfbase)/lilypond-book . && \ - ln -sf ../../scripts/$(outconfbase)/*.ly . + for i in abc2ly convert-ly etf2ly lilypond-book lilypond-invoke-editor midi2ly musicxml2ly; \ + do ln -sf ../../scripts/$(outconfbase)/$$i . ; done cd $(tree-lib-prefix) && \ ln -s ../../../../python/$(outconfbase) python cd $(tree-share-prefix) && \ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: out/bin/*.ly ?
Karl Hammar schreef: What is the meaning of *.ly which point to nothing below ? $ ls -l out/bin/ total 0 lrwxrwxrwx 1 karl users 22 May 22 17:57 *.ly -> ../../scripts/out/*.ly lrwxrwxrwx 1 karl users 28 May 22 17:57 convert-ly -> ../../scripts/out/convert-ly lrwxrwxrwx 1 karl users 23 May 22 17:57 lilypond -> ../../lily/out/lilypond lrwxrwxrwx 1 karl users 31 May 22 17:57 lilypond-book -> ../../scripts/out/lilypond-book $ Maybe it should read ln -s .../*2ly . instead of *.ly ? If so, use attached patch. Also note that target $(tree-share-prefix)/lilypond-force in toplevel GNUmakefile is run before the generation of the files in scripts/out/ so any wildcard are useless in the line above, and will generate the file *.ly instead of expanding to future files. * GNUmakefile.in: wildcard in ln -s .../*.ly . don't work when newly checkout'ed thanks. applied. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: maze of documentation GNUmakefiles
Graham Percival schreef: Documentation/user/ requires "texi2dvi -E..." as a workaround for a texinfo bug. (Karl said that he'd try to investigate it tomorrow morning) input/* requires texi2dvi without the -E. I tried making a stepmake/stepmake/texinfoB-rules.make which includes the -E, and then modifying Documentation/user/GNUmakefile to use STEPMAKE_TEMPLATES=tex texinfoB omf documentation but it still used the normal texinfo rules (with no -E). How can I have Hi, Because I want to release 2.9.6, I've redefined @funindex to be a null operation. -E also doesn't work for music-glossary, so I've switched that off again. I think the best is to wait for the texinfo people to sort out the problem and produce a texinfo patch. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Yet another 2 patches for music streams
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > Erik Sandberg schreef: >> On Tuesday 23 May 2006 13:01, Han-Wen Nienhuys wrote: >>> *Please commit the 1st patch after lyricsto works again. >> I have committed now. There are two problems still, whihc I ignored >> (they do not affect make web): >> - input/no-notation/denneboom.ly uses \oldaddlyrics. However, it >> didn't work before my patch either, so I guess the file is obsolete >> anyways > > yes, removed. > >> - input/no-notation/display-lily-tests.ly also contains an >> oldaddlyrics reference, but lily fails on the file anyway. > > Hmm. Nicolas? it should be fixed now ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
broken by latest patch:
Hi Erik, I suspect that the following failing regtests relates to your changes. Can you analyze? alignment-vertical-spacing.ly alignment-vertical-manual-setting.ly dynamics-broken-hairpin.ly thanks! -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
configure find wrong python path
Given: $ ls -l /usr/bin/python* lrwxrwxrwx 1 root root 9 May 24 15:51 /usr/bin/python -> python2.3 -rwxr-xr-x 1 root root 958764 Mar 6 11:32 /usr/bin/python2.3 -rwxr-xr-x 1 root root 1024460 Apr 23 01:34 /usr/bin/python2.4 configure will report wrong path of python: $ ./configure ... checking for bash... /bin/sh checking for python... python checking python version... 2.3.5 checking for python... /usr/bin/python checking for gcc... gcc ... checking New Century Schoolbook PFB files... /usr/share/fonts/type... checking for python... /usr/bin/python checking /usr/bin/python version... 2.3.5 python checking python version... 2.3.5 python2 python2.4 checking python2.4 version... 2.4 checking for python2.4... (cached) /usr/bin/python checking gcc version... 4.0.3 ... $ make ... import subprocess ImportError: No module named subprocess make[2]: *** [out/lilypond.nexi] Error 1 make[2]: Leaving directory `/home/karl/most/music/lilypond/head/Documentation/user' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/karl/most/music/lilypond/head/Documentation' make: *** [all] Error 2 $ STEPMAKE_PYTHON is run twice during configure: STEPMAKE_PYTHON(REQUIRED, 1.5) configure.in line 15: STEPMAKE_INIT() -> stepmake/aclocal.m4 line 755 and STEPMAKE_PYTHON(REQUIRED, 2.4) configure.in line 87. STEPMAKE_PYTHON() calls AC_PATH_PROG() which calls AC_CACHE_VAL([ac_cv_path_$1], ... ) The second time AC_PATH_PROG() takes path from cache as seen in configure trace above. Since STEPMAKE_PYTHON() have a second argument (req. version) and the cache don't know of versions, one should clear the cache when seraching for a new python path. Attached patch corrects the error above. * stepmake/aclocal.m4: STEPMAKE_PYTHON(): clear cached value since arg 2 might point us to a new binary Regards /Karl Index: stepmake/aclocal.m4 === RCS file: /sources/lilypond/lilypond/stepmake/aclocal.m4,v retrieving revision 1.168 diff -u -r1.168 aclocal.m4 --- stepmake/aclocal.m4 3 May 2006 20:30:59 - 1.168 +++ stepmake/aclocal.m4 24 May 2006 21:18:50 - @@ -994,6 +994,8 @@ if test -n "$pv"; then STEPMAKE_ADD_ENTRY($1, $pv) fi +# clear cached value since arg 2 might point us to a new binary +unset ac_cv_path_PYTHON AC_PATH_PROG(PYTHON, $PYTHON) AC_SUBST(PYTHON) ]) ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
addition to documentation - ghost notes for drums/percussion
(append to section 7.4.3 ? or add new 7.4.4 ?)
Ghost notes
Ghost notes for drums and percussion can be created by using the
/parenthesize prefix (see 8.5.8), however by default /drummode does
not include the Parenthesis_engraver plugin which allows this. You
must add the plugin explicitly in the context definition (see 9.2.3).
For example:
\new DrumStaff \with { \consists "Parenthesis_engraver" } <<
\context DrumVoice = "1" { s1 *2 }
\context DrumVoice = "2" { s1 *2 }
\drummode {
<<
{ hh8[ hh] hh16 < \parenthesize sn > hh < \parenthesize
sn > hh8 hh }
\\
{ bd4 r4 bd8 bd r8 bd }
>>
}
Also note that you must add "< >" brackets around each /parenthesize statement.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
