Re: Waltrop meeting outline
Thanks, I'm almost on the way! Am 26.08.2012 um 02:07 schrieb David Kastrup: pls p.l.schm...@gmx.de writes: I'll try to be in Brambauer at 11:09. If you haven't ordered food yet I'd take the Broccoli al Forno. Otherwise: no problem. If possible, call when you are in the subway. 02309-782756 landline, probably less reliable fallback 016092087547. I'll call the cook in the morning (probably getting the answering machine, but that should suffice). -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Issue 1236: CG+scripts should use $LILYPOND_GIT (issue 6483057)
LGTM, thanks! http://codereview.appspot.com/6483057/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
contributor's guide 10.2.8 Python
Hi, 10.2.8 of the contributors guide says Python is used for XML2ly and is building the documentation and the website Sounds a bit incomplete to me. XML2ly is musicxml2ly I guess. And what about midi2ly, lilypond-book, abc2ly, convert-ly? Also I was hoping to find info about the required/recommended Python version here when I was browsing the docs. Maybe that info can be found somewhere else? BTW: Are there any thoughts about switching from Python 2.x to Python 3.x somewhere in the future? -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: contributor's guide 10.2.8 Python
- Original Message - From: Martin Tarenskeen m.tarensk...@zonnet.nl To: lilypond-devel mailinglist lilypond-devel@gnu.org Sent: Sunday, August 26, 2012 11:06 AM Subject: contributor's guide 10.2.8 Python Hi, 10.2.8 of the contributors guide says Python is used for XML2ly and is building the documentation and the website Sounds a bit incomplete to me. XML2ly is musicxml2ly I guess. And what about midi2ly, lilypond-book, abc2ly, convert-ly? I think you're right. A patch to correct this would be welcome. Also I was hoping to find info about the required/recommended Python version here when I was browsing the docs. Maybe that info can be found somewhere else? It looks like the Python on my windows install is 2.4.5. BTW: Are there any thoughts about switching from Python 2.x to Python 3.x somewhere in the future? I don't believe so. A lot of the GUB build relies on Python, and it also creates a shipping Python by a mechanism I don't believe anyone currently understands. Is there a good reason to want to? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 1236: CG+scripts should use $LILYPOND_GIT (issue 6483057)
second thought, there's two remaining ones that should be changed: quick-start.itexi: line 285 programming-work.itexi: line 982 http://codereview.appspot.com/6483057/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [Lilypond-auto] Patchy email
Hi James, 09:24:02 (UTC) Begin LilyPond compile, previous commit at d14e4770b85b3cacc647e45b9ebfe59cc085753f 09:24:07 Merged staging, now at: d14e4770b85b3cacc647e45b9ebfe59cc085753f 09:24:08Success:./autogen.sh --noconfigure 09:24:18Success:../configure --disable-optimising 09:24:24Success:nice make clean 09:25:34Success:nice make -j7 CPU_COUNT=7 09:27:51Success:nice make test -j7 CPU_COUNT=7 09:44:13Success:nice make doc -j7 CPU_COUNT=7 09:44:17 *** FAILED STEP *** merge from staging Command '['git', 'log', '-1', 'origin/HEAD..test-staging']' returned non-zero exit status 128 fatal: ambiguous argument 'origin/HEAD..test-staging': unknown revision or path not in the working tree. Use '--' to separate paths from revisions I suppose that your $LILYPOND_GIT git repository has fetch settings that differ from ours, so you got this error, and in addition I guess that master and HEAD should always be equal on Savannah LilyPond git repo. Could please you help me with verifying the first guess by answering the following? 1) What does cd $LILYPOND_GIT git rev-parse origin/HEAD say? 2) What does the [remote origin] section of $LILYPOND_GIT/.git/config contain? 3) What does lilypond-patchy-staging say (complete console output) if you replace line 334 of patches/compile_lilypond_test/__init__.py origin_head = remote_branch_name (HEAD) with origin_head = remote_branch_name (master) ? (In case after the change lilypond-patchy-staging says No new commits, clear the value of last_known_good_build in [staging] section of ~/.lilypond-patchy-config and rerun lilypond-patchy-staging). Thanks, John ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 1236: CG+scripts should use $LILYPOND_GIT (issue 6483057)
Am 26.08.2012 12:32, schrieb gra...@percival-music.ca: second thought, there's two remaining ones that should be changed: quick-start.itexi: line 285 programming-work.itexi: line 982 There you are. http://codereview.appspot.com/6483057/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: contributor's guide 10.2.8 Python
On Sun, Aug 26, 2012 at 11:14:06AM +0100, Phil Holmes wrote: - Original Message - From: Martin Tarenskeen m.tarensk...@zonnet.nl To: lilypond-devel mailinglist lilypond-devel@gnu.org Also I was hoping to find info about the required/recommended Python version here when I was browsing the docs. Maybe that info can be found somewhere else? It looks like the Python on my windows install is 2.4.5. Yes. All lilypond scripts must work on python 2.4.5 or maybe even 2.4.2. This causes problems because everybody uses+tests stuff with python 2.6 or 2.7, and we only discover the 2.4.5 problem while building the binaries. BTW: Are there any thoughts about switching from Python 2.x to Python 3.x somewhere in the future? I don't believe so. A lot of the GUB build relies on Python, and it also creates a shipping Python by a mechanism I don't believe anyone currently understands. Is there a good reason to want to? Jan and John have spent most of the past 2 days working on GUB side-by-side, and they're likely to spend most of today doing the same. Changing to python 3 would be far more intrusive than updating to python 2.7, but even python 2.7 is likely out of reach from a mere 4 days of solid work from two of our best build system hackers. If anybody's interested in this stuff, then please check out the GUB repo. Right now all work is done on the Waltrop branch, but we'll be merging that with master soon. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [Lilypond-auto] Patchy email
John, On 26 August 2012 11:39, John Mandereau john.mander...@gmail.com wrote: Hi James, 09:24:02 (UTC) Begin LilyPond compile, previous commit at d14e4770b85b3cacc647e45b9ebfe59cc085753f 09:24:07 Merged staging, now at: d14e4770b85b3cacc647e45b9ebfe59cc085753f 09:24:08Success:./autogen.sh --noconfigure 09:24:18Success:../configure --disable-optimising 09:24:24Success:nice make clean 09:25:34Success:nice make -j7 CPU_COUNT=7 09:27:51Success:nice make test -j7 CPU_COUNT=7 09:44:13Success:nice make doc -j7 CPU_COUNT=7 09:44:17 *** FAILED STEP *** merge from staging Command '['git', 'log', '-1', 'origin/HEAD..test-staging']' returned non-zero exit status 128 fatal: ambiguous argument 'origin/HEAD..test-staging': unknown revision or path not in the working tree. Use '--' to separate paths from revisions I suppose that your $LILYPOND_GIT git repository has fetch settings that differ from ours, so you got this error, and in addition I guess that master and HEAD should always be equal on Savannah LilyPond git repo. Could please you help me with verifying the first guess by answering the following? 1) What does cd $LILYPOND_GIT git rev-parse origin/HEAD say? --snip- james@jameslilydev2:~/patchy/test-results$ cd $LILYPOND_GIT james@jameslilydev2:~/lilypond-git$ git rev-parse origin/HEAD origin/HEAD fatal: ambiguous argument 'origin/HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions --snip-- 2) What does the [remote origin] section of $LILYPOND_GIT/.git/config contain? [remote origin] url = ssh://pkx1...@git.sv.gnu.org/srv/git/lilypond.git fetch = +refs/heads/*:refs/remotes/origin/* 3) What does lilypond-patchy-staging say (complete console output) if you replace line 334 of patches/compile_lilypond_test/__init__.py origin_head = remote_branch_name (HEAD) with origin_head = remote_branch_name (master) ? Unfortunately I think that Phil's successful merge will make this redundant at this moment but I did it anyway --snip-- From ssh://git.sv.gnu.org/srv/git/lilypond + 9c9d22c...4de3d0d release/unstable - origin/release/unstable (forced update) 11:07:22 (UTC) Begin LilyPond compile, previous commit at d14e4770b85b3cacc647e45b9ebfe59cc085753f 11:07:32Success:No new commits in staging --snip-- (In case after the change lilypond-patchy-staging says No new commits, clear the value of last_known_good_build in [staging] section of ~/.lilypond-patchy-config and rerun lilypond-patchy-staging). ah.. ok :) --snip-- james@jameslilydev2:~/patchy/patches/compile_lilypond_test$ ../lilypond-patchy-staging.py Everything up-to-date --snip-- No errors james ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
demerit in Slur_configuration::score_edges
Question - with the demerit in this function, on line 436 (the initialization of demerit), why are we multiplying by dy? I would have thought that if the span of dy were larger, we would want the demerit to be smaller so that the slur was less bound to the edges. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
developer chats
Let's give this another try. Anybody interested in setting up a regular weekly chat? Either IRC or skype or some other chat protocol. The idea is that we'd pick some time (say, 19:00 UTC on Tuesdays -- but that's a completely random time), then whoever wanted to hang out could come by. Or, if there's enough interested (particularly from people in time zones which don't work well with 19:00 UTC), we could have two chats at different times. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: demerit in Slur_configuration::score_edges
On Sun, Aug 26, 2012 at 10:01 AM, m...@mikesolomon.org m...@mikesolomon.org wrote: Question - with the demerit in this function, on line 436 (the initialization of demerit), why are we multiplying by dy? I would have thought that if the span of dy were larger, we would want the demerit to be smaller so that the slur was less bound to the edges. AFAICS, this is designed so the ends of the slur stay close to base_attachment_ -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Many changes to Patchy
Hi guys, After lots of testing, debugging, and commits editions cycles, I've pushed many changes to Patchy in lilypond-extra master branch. Most changes regard Patchy on a server and patches testing. These changes are expected to make existing Patchy setups work at least as well as before; on the contrary, please complain by replying to this message, or send a report on this list. Among the new features, which you can have a glance at in the git log: * optionally build the docs when testing patches (in the section [compiling], set the option patch_test_build_docs to yes, and if you remember to clean out test results often or have a TB of free space, you can set patch_test_copy_docs to yes too), * limit resources used by the build; for adjusting settings in [self_limits] and [runner_limits] configuration sections, see http://docs.python.org/library/resource.html and man setrlimit, * more configurable email notifications. Hopefully enjoy! Best, John ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Check for Fontforge with enable-double (1637) (issue 6484062)
LGTM, I get the expected error from a stock ubuntu 12.04 (which does not include --enable-double). http://codereview.appspot.com/6484062/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Check for Fontforge with enable-double (1637) (issue 6484062)
LGTM except one nitpick (see comment). http://codereview.appspot.com/6484062/diff/1/configure.in File configure.in (right): http://codereview.appspot.com/6484062/diff/1/configure.in#newcode174 configure.in:174: if $FONTFORGE --version 21|egrep -q -e '-L?D\.?$'; then It seems that egrep vs. grep and egrep/grep -e flag are redundant, why not just have grep -q -e instead? http://codereview.appspot.com/6484062/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCH: Countdown to 20120828
For 20:00 MDT Tuesday August 28 Documentation: Issue 2660 http://code.google.com/p/lilypond/issues/detail?id=2660: add website link to tunefl.com - R 6486067 http://codereview.appspot.com/6486067/ Issue 2652 http://code.google.com/p/lilypond/issues/detail?id=2652: If the book only has a single score, the \header block may be placed inside or outside of the \score block - R 6474066 http://codereview.appspot.com/6474066/ Maintainability: Issue 1236 http://code.google.com/p/lilypond/issues/detail?id=1236: CG+scripts should use $LILYPOND_GIT - R 6483057 http://codereview.appspot.com/6483057/ Ugly: Issue 728 http://code.google.com/p/lilypond/issues/detail?id=728: Fingerings collide with accidentals. - R 6485068 http://codereview.appspot.com/6485068/ Issue 2148 http://code.google.com/p/lilypond/issues/detail?id=2148: vertical skylines should use stencil integrals - R 5626052 http://codereview.appspot.com/5626052/ Issue 2284 http://code.google.com/p/lilypond/issues/detail?id=2284: Clef 'Octavation number' collides with Beam - R 6475065 http://codereview.appspot.com/6475065/ Issue 2764 http://code.google.com/p/lilypond/issues/detail?id=2764: Fingering placement problem in chords containing a second - R 6472056 http://codereview.appspot.com/6472056/ Cheers, Colin -- Criticism, like rain, should be gentle enough to nourish a man's growth without destroying his roots. - Frank A. Clark, writer (1911- ) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
