Re: critical issues
Hello, 2012/1/8 Łukasz Czerwiński milimet...@gmail.com: What's the aim of Lilypond? err.. LilyPond is a music engraving program, devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts. And why isn't it competing with Finale and Sibellius? Aren't all three programs making PDF files with music? Of course Finale and Sibellius have some other functionalities, but the common one is related to PDFs. Every computer program and in fact every thing or machine have a most common user. How would you describe a most common user of Lilypond? How does he/she use Lilypond, what kind of music (and how complex) does they (re-)write? What annoys or disturbs them most in Lilypond? I keep re-reading this and I just think you want a nice point-and-click GUI. I don't know what else it is you seem to want apart from to say LilyPond is 'better' than Sibelius/Finale' in some vague and probably meaningless way. Sibelius and Finale cost hundreds of pounds, LilyPond is free, there is no 'competition'. The output of LP in 99% of cases is much better out of the box than any of those packages can manage - I know, I have to sit in my orchestra and read the crud that comes out of the Sib/Fib stuff. I can use LilyPond on all the 3 platforms (MacOS, Windows and Linux) that I use, without any problems at all, move files between the two. I can use any editor I choose (again important when using 3 different platforms), the files I use are easily read on *any* version of LilyPond and apart from the odd complex syntax change of which we have a simple script to help (convert-ly) I don't have to worry much about forward incompatibility. There is no typical user, that is a myth as I am sure it is the same in Sib/Fib. If you are talking about MIDI output, LilyPond was never intended for that, it's nice that we have some 'relatively ok' capabilities (no offence to the MIDI coders - I rarely use MIDI anyway) but all the Sib/Fib people I know don't use MIDI either, but there are much much better (and free) tools to produce midi output than Sib/Fib anyway. if yuo haven't already then I suggest you read http://lilypond.org/freedom.html http://lilypond.org/reviews.html http://lilypond.org/essay.html Pretty much says it all. Let's assume that I would like to help in developing Lilypond, but I don't have my own idea, what part of it I could improve. What would you suggest me to do? Start by looking here: http://code.google.com/p/lilypond/issues/list?can=2q=sort=prioritycolspec=IDx=typey=prioritymode=gridcells=tiles Take your pick! If everybody does it in his own local way, it is more a distraction than anything else. How does one do x in LilyPond? Depends on whether you are talking about functionality written by Mike, David, Han-Wen, Jan, Graham, Carl or Werner. That's not what a user wants to hear. Are there some guidelines how to write new code to work in the same manner as the already written code? Start here: http://lilypond.org/doc/v2.15/Documentation/contributor/summary-for-experienced-developers Else: http://lilypond.org/doc/v2.15/Documentation/contributor/help-us If no, is there a person (several people?) that could answer such questions? lilypond-devel@gnu.org -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: bar-chords-notation-for-guitar--with-text-spanner.ly (was Re: staging-broken-jan7)
Mike On 8 January 2012 12:48, m...@apollinemike.com m...@apollinemike.com wrote: Hey all, On my lilybuntu box, I am consistently getting a doc fail from current master on this file. The problem is the embedded post script. It seems like it's a ghostscript error: Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./bar-chords-notation-for-guitar--with-text-spanner.pdf -c.setpdfwrite -fbar-chords-notation-for-guitar--with-text-spanner.ps'... GPL Ghostscript 8.71 (2010-02-10) Are you using LilyDev2.0? -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: bar-chords-notation-for-guitar--with-text-spanner.ly (was Re: staging-broken-jan7)
Hello, On 8 January 2012 13:07, James pkx1...@gmail.com wrote: Mike On 8 January 2012 12:48, m...@apollinemike.com m...@apollinemike.com wrote: Hey all, On my lilybuntu box, I am consistently getting a doc fail from current master on this file. The problem is the embedded post script. It seems like it's a ghostscript error: Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./bar-chords-notation-for-guitar--with-text-spanner.pdf -c.setpdfwrite -fbar-chords-notation-for-guitar--with-text-spanner.ps'... GPL Ghostscript 8.71 (2010-02-10) Ah I have a LilyDev 2.0 at work, so I checked I too have version 7.1 installed and that would be the one I use 'at home' (I build doc two days ago with no problems). There *is* a GS update if you run the LilyDev 'check for updates' thingy (or run sudo apt-get update/upgrade). But I deliberately haven't upgrade GS yet because of issues in the past and because it is fundamental to building doc). So it seems you have the same as I. I'll build LP in the current master on my side in LilyDev and then try this file. I'll use ../configure without the disable-optimising only because you probably use that switch by default, and let you know. My work LilyBuntu is much less powerful than my home one so it takes a few minutes... -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: easiest way to help releases: adopt patchy
Graham, On 8 January 2012 13:39, Graham Percival gra...@percival-music.ca wrote: Patchy has helped us avoid breaking git master a few times recently, but each time involves a certain amount of my time and energy. I need to check the logs to see if it was just an accident, look through the git history to see if there's any particularly suspicious commits that may have caused it, try again without those commits, repeat, and then finally branch the entire staging and start over from scratch. This eats up time that I could otherwise spend on releases or organizing stuff. Nothing in Patchy requires my unique skills. There's a few more things that could be done to improve things, but those can pretty much just follow the existing pattern. If somebody else could take over Patchy -- even if only the staging stuff, not the new patches -- that would free up time I could spend solving release-critical bugs. If somebody could handle the new patches as well, that would be even better. We could easily have two separate people doing staging and new patches. I can do that, I assume it was pretty much what I was doing with the early itteration of whatever script was on your https://github.com/gperciva/lilypond-extra site. I'm not able to do any python tweaking but I can run stuff and check things like I used to do. Let me know and if there are any specific instructions I need to set up. -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: bar-chords-notation-for-guitar--with-text-spanner.ly (was Re: staging-broken-jan7)
Mike On 8 January 2012 12:48, m...@apollinemike.com m...@apollinemike.com wrote: Hey all, On my lilybuntu box, I am consistently getting a doc fail from current master on this file. The problem is the embedded post script. It seems like it's a ghostscript error: Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./bar-chords-notation-for-guitar--with-text-spanner.pdf -c.setpdfwrite -fbar-chords-notation-for-guitar--with-text-spanner.ps'... I can run lilypond on this file bar-chords-notation-for-guitar--with-text-spanner.ly directly with no problems after building from current master. I'll kick off a make doc but that will take this machine I have a good 45 minutes or so. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: easiest way to help releases: adopt patchy
Graham, On 8 January 2012 13:55, Graham Percival gra...@percival-music.ca wrote: On Sun, Jan 08, 2012 at 01:46:44PM +, James wrote: If somebody else could take over Patchy -- even if only the staging stuff, not the new patches -- that would free up time I could spend solving release-critical bugs. If somebody could handle the new patches as well, that would be even better. I can do that, I assume it was pretty much what I was doing with the early itteration of whatever script was on your https://github.com/gperciva/lilypond-extra site. I'm not able to do any python tweaking but I can run stuff and check things like I used to do. Let me know and if there are any specific instructions I need to set up. Start by running lilypond-patchy-staging.py. You'll need to tweak the config file so it emails you instead of me. Once you've run it a few times manually and had it work, stick it in a cronjob. Whenever it breaks, find out why, deal with the commits, etc. OK no problem. I'll not get to this proper until this evening and then only to give it a once over - I'm sure it will be as before - but I'll aim to start using it 'in anger' by tomorrow evening if that's ok? regards -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: bar-chords-notation-for-guitar--with-text-spanner.ly (was Re: staging-broken-jan7)
Mike On 8 January 2012 12:48, m...@apollinemike.com m...@apollinemike.com wrote: Hey all, On my lilybuntu box, I am consistently getting a doc fail from current master on this file. The problem is the embedded post script. It seems like it's a ghostscript error: I'm not getting this. My make doc is still going but it's gone past the point of where I would expect this error to occur. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Reorganize NR 1.3 Expressive marks
Xavier, On 8 January 2012 21:08, Xavier Scheuer x.sche...@gmail.com wrote: Hi James, Currently we have snippets about DynamicTextSpanner both in NR 1.3.1 Expressive marks attached to notes Dynamics and in NR 1.8.1 Writing text Text spanners . It would be more consistent to have everything about DynamicTextSpanner in the same section of the NR, i.e. NR 1.3.1, with a cross-reference to this section in NR 1.8.1. But that would make a lot of snippets about dynamics together. Why not make a specific section of NR 1. Musical notation about dynamics (e.g NR 1.3 Dynamics , containing what is currently in Dynamics and New dynamic marks + the snippets moved from NR 1.8.1), and another section for the other expressive marks attached to notes (NR 1.4 Expressive marks attached to notes containing in the order Articulations and ornamentations, Trills, Slurs, Breath marks, Falls and doits, Glissando, Arpeggio)? I'd suggest something like: NR 1.3 Dynamics 1.3.1 Dynamic marks 1.3.2 Hairpins 1.3.3 Dynamic text spanners 1.3.4 New dynamic marks 1.3.5 Custom dynamic text spanners NR 1.4 Expressive marks 1.4.1 Articulations and ornamentations Articulations and ornamentations, Trills (with trills together) 1.4.2 Curves Slurs (with a warning cross-ref about ties), Phrasing slurs, Breath marks, Falls and doits 1.4.3 Lines Glissando, Arpeggio (but not trills here) We could add something about the horizontal line that means keep the finger, keep the position or stay on the same string. What do you think? I think we need to have some feedback from Graham the Doc Meister and Trevor (who both did most of the Documentation). Then assuming this has approval then we need a tracker (or 2, maybe 3) to manage this, it certainly won't be something we should be doing in a single patch. It looks nice on paper, but when you get down to it - as I started to with http://code.google.com/p/lilypond/issues/detail?id=1287 It isn't as trivial as you think - and can end up a lot of work, and while I understand the request, there are more pressing items I think we need to do with the doc before we start to move huge sections around. I'd personally like to get the the 50% or so of the current tracker items done first http://code.google.com/p/lilypond/issues/list?can=2q=type=Documentationcolspec=IDsort=priorityx=typey=prioritycells=tilesmode=grid If you can help on any of these that would be useful. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Make grand-replace
Hello, I noticed this command http://lilypond.org/doc/v2.15/Documentation/contributor/unsorted-policies :) So I tried it... Gosh... that command touches 'one or two' files doesn't it! chuckle Umm.. I guess this is something that a 'senior' dev probably should do as it also touches all the translated files too. Maybe on the next dev release? Regards -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob (issue 5527058)
On 9 January 2012 20:49, carl.d.soren...@gmail.com wrote: Looks *very* good to me! I really like having only one \footnote command; it's intuitive for users. Thanks for doing this! On the shoulders of Giants eh David ;) I can help with the doc if you like, perhaps download the diff file from the tracker, apply it and give it back for you to apply on your patch? -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Production with LilyPond
hello, On 12 January 2012 05:47, Graham Percival gra...@percival-music.ca wrote: On Wed, Jan 11, 2012 at 12:19:27PM +0100, Janek Warchoł wrote: 2012/1/10 Xavier Scheuer x.sche...@gmail.com: I guess this message would be more appropriate on lilypond-u...@gnu.org rather than on the bug reports mailing list. May I suggest you to send it (again) to this address, thus reaching the LilyPond Users community? Sending such information to bug reports list looks strange to me too, however http://lilypond.org/productions.html says exactly to do this - maybe it shouldn't say so? What on earth are you talking about? bug-lilypond is the place for users to report matters that are of interest to developers. Aurélien reported it there. James will hopefully be acting on his report. This is working exactly as it should. http://code.google.com/p/lilypond/issues/detail?id=2218 James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Undefined references in translated manuals (issue 2220). (issue 5539052)
On 13 January 2012 08:42, paconet@gmail.com wrote: Some of these changes are already pushed. I could kiss myself. can I kiss someone? Hey perhaps we need a Kissmeister... any takers? Janek? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Clickable examples in the docs
Hello, On 15 January 2012 17:03, Federico Bruni fedel...@gmail.com wrote: Il 15/01/2012 17:51, Neil Puttock ha scritto: I'm not sure how long it's been like this; I only noticed it when I looked at the changes page today. I noticed it ten days ago and forgot to report it (sorry). Opened as: http://code.google.com/p/lilypond/issues/detail?id=2224 -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH 1/2] Fix spelling definiton - definition
Jean-Charles, On 20 January 2012 08:02, Lilyfan lily...@orange.fr wrote: Message du 20/01/12 03:42 De : Stefan Weil A : lilypond-devel@gnu.org Copie à : Stefan Weil Objet : [PATCH 1/2] Fix spelling definiton - definition Signed-off-by: Stefan Weil --- po/cs.po ... Please *never* patch the po directory: all translations transit on the Free Translation Project. The master file, lilypond.pot, is generated by a dedicated script I will run when 2.16-RC1 comes out. The po files are to the responsability of a due translator who willl send his updated native po file to the FTP. Should we mention this in the Contributor Guide somewhere - Documentation Translation didn't seem the appropriate place? Regards -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Spelling fixes
Hello, On 20 January 2012 16:58, Stefan Weil s...@weilnetz.de wrote: Hi, my last two patches were sent inline (with git send-email), but I just learned that they should have been appended instead. So here are both patches again. Both fix some spelling issues. Kind regards, Stefan Weil I'd offer to manage these but I guess it is better handled by someone who understands the translation branches? -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Spelling fixes
Stefan, On 21 January 2012 07:23, Stefan Weil s...@weilnetz.de wrote: Am 21.01.2012 00:10, schrieb Pavel Roskin: On Fri, 20 Jan 2012 17:58:47 +0100 Stefan Weils...@weilnetz.de wrote: Hi, tre my last two patches were sent inline (with git send-email), but I just learned that they should have been appended instead. So here are both patches again. Both fix some spelling issues. By the way, somebody please run codespell on the Lilypond sources: http://git.profusion.mobi/cgit.cgi/lucas/codespell/ Hi Pavel, that's what I did. I started with three patches, but as soon as I know that they are accepted, more will follow. Your two patches have been opened as http://code.google.com/p/lilypond/issues/detail?id=2237 http://code.google.com/p/lilypond/issues/detail?id=2238 The code is uploaded for review and comment to http://codereview.appspot.com/5562043 and http://codereview.appspot.com/5561053 I 'own' these issues but if you get reqests for changes you can just upload the changes to 'codereview' yourself (if you know how to do that) or you can attach any corrected patches to the code.google issues and I can re-submit them. The process is documented here: http://lilypond.org/doc/v2.15/Documentation/contributor/summary-for-experienced-developers (start at 'reviews' in this case) -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Spelling fixes
Stefan, On 21 January 2012 07:23, Stefan Weil s...@weilnetz.de wrote: Am 21.01.2012 00:10, schrieb Pavel Roskin: On Fri, 20 Jan 2012 17:58:47 +0100 Stefan Weils...@weilnetz.de wrote: Hi, tre my last two patches were sent inline (with git send-email), but I just learned that they should have been appended instead. So here are both patches again. Both fix some spelling issues. By the way, somebody please run codespell on the Lilypond sources: http://git.profusion.mobi/cgit.cgi/lucas/codespell/ Hi Pavel, that's what I did. I started with three patches, but as soon as I know that they are accepted, more will follow. http://code.google.com/p/lilypond/issues/detail?id=2237 (the texidoc corrections) Has been approved and pushed to our staging branch. It will be merged in to the master branch soon. Thanks for the patch. The other I am leaving the other for a more thorough review -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Update lilygit.tcl (Issue 2092) (issue 5504092)
Hello On 21 January 2012 21:12, janek.lilyp...@gmail.com wrote: Some questions and concerns. While I don't understand any of this really, isn't lily-git.tcl supposed to be for git-idiots (like me) who don't even want to think about branches? :) Just wondering if Janek is 'overthinking' this - apologies if not. Also @carl, could we make lilygit-tcl (not this patch) with a text area I can *paste* into (and/or ctrl-v) as I cannot do that with the current iteration, I can only type into it. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make doc problem
Hello, On 22 January 2012 20:05, David Kastrup d...@gnu.org wrote: Julien Rioux jri...@physics.utoronto.ca writes: Thanks, you're quite right CPU is not the limiting factor for the build. Disk access and usage of swap when compiling input/regression/collated-files slows down the build to a crawl for me. If it is really usage of swap: getting more memory will be by far the cheapest method of speeding up your computer much more than buying a faster CPU ever could. getting an SSD will also help if you have run out of memory slots to fill. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: somebody needs to run staging before 29 Jan
Hello, On 24 January 2012 22:20, David Kastrup d...@gnu.org wrote: Janek Warchoł janek.lilyp...@gmail.com writes: Keeping the staging-merge going would be about five people committing to 50€ a month. That is, of course, not enough for me to live on. It merely means that taking on this duty will not further reduce the amount of time I can spend on LilyPond in total. That would be a waste of your skills. The skills will eventually become unavailable anyway if nobody pays for either major or minor variants of them, so that should be the smallest worry. I have not offered to do it for free, anyway. If the time I spend on that is paid for, it is no loss to anybody. I don't have a 24/7 computer, Neither is a laptop, but I'd still get some stuff done. but if no one else will volunteer i can run Patchy (the skills necessary are quite like mine). I only need to pass my exams - 9 days left till i have lots of time to investigate and improve Patchy (with Julien's help). I have a machine that I can keep running 24/7 (well I have electricity 24/7, Internet connection probably about 20/7) and have already offered (and been trying) to run patchy but with limited success this week. I haven't bothered Graham as he is on limited time now, which can be better spent I am sure that walking me through python scripts. However when I run patchy I am getting --snip-- james@jameslilydev2:~/Desktop/patchy$ ./run-lilypond-staging.sh remote: Counting objects: 83, done. remote: Compressing objects: 100% (57/57), done. remote: Total 57 (delta 45), reused 0 (delta 0) Unpacking objects: 100% (57/57), done. From ssh://git.sv.gnu.org/srv/git/lilypond 39f5057..5a61803 master - origin/master ad3a9e6..8019ff7 staging- origin/staging From ssh://git.sv.gnu.org/srv/git/lilypond * [new tag] release/2.15.27-1 - release/2.15.27-1 Branch test-master-lock set up to track remote branch master from origin. Branch test-staging set up to track remote branch staging from origin. Initialized empty Git repository in /home/james/Desktop/patchy/lilypond-autobuild/.git/ fatal: attempt to fetch/clone from a shallow repository fatal: The remote end hung up unexpectedly Begin LilyPond compile, commit: 39f50579ff91fdca06acd52a9392ab2874f4723b etc etc. --- and I don't know where I need to look from here. Bear in mind this is on my lilydev machine where I can manually download/git pull/push etc. So I know it is getting the code but not sure what the other message means because it is coming from git (I cannot find the 'fatal' strings in any of the .py files). I'm struggling to find time between my coffee and cornflakes as well as doing doc patches, so if someone can shed any light or point me somewhere I can move on with Patchy. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy email
Julien, On 28 January 2012 13:31, Julien Rioux julien.ri...@gmail.com wrote: On Sat, Jan 28, 2012 at 7:27 AM, Graham Percival gra...@percival-music.ca wrote: On Sat, Jan 28, 2012 at 04:18:00AM -0800, lilypond.patchy.gra...@gmail.com wrote: *** FAILED BUILD *** nice make test -j3 CPU_COUNT=3 Previous good commit: 05efb98f2e3ff68f4bb8221db640b0174bfcde93 Current broken commit: b445e1b4207996eee2362187fa3e8b8af8ff05ba make[1]: *** [out-test/tex-fragment.tex] Error 1 make[1]: *** Waiting for unfinished jobs - Graham I don't use patchy but checking out staging just now, I run ./configure ; make -j8 CPU_COUNT=8 ; This was all fine. When I ran make doc (make -j8 CPU_COUNT=8 doc) it 'nearly' completed. The last lot of log I got was --snip-- Success: compilation successfully completed Writing /home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-1.signature Layout output to `/home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554.pdf'... Layout output to `/home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-1.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-1.pdf'... Preprocessing graphical objects... Layout output to `/home/james/lilypond-git/build/out/lybook-db/30/lily-10fcfa18-1.eps'... Could not overwrite file /home/james/lilypond-git/build/input/regression/lilypond-book/out-www/08/lily-015b46b4.png Converting to `/home/james/lilypond-git/build/out/lybook-db/30/lily-10fcfa18-1.pdf'... make[4]: *** [out-www/html-space-after-tag.html] Error 1 Layout output to `/home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-1.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-1.pdf'... Calculating line breaks... Drawing systems... Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.texi... Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.tex... Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.count...Converting to PNG... Writing /home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-1.signature Layout output to `/home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4.pdf'... Writing /home/james/lilypond-git/build/out/lybook-db/30/lily-10fcfa18-systems.texi... Writing /home/james/lilypond-git/build/out/lybook-db/30/lily-10fcfa18-systems.tex... Writing /home/james/lilypond-git/build/out/lybook-db/30/lily-10fcfa18-systems.count...Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.texi... Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.tex... Writing /home/james/lilypond-git/build/out/lybook-db/08/lily-015b46b4-systems.count... Success: compilation successfully completed Layout output to `/home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-1.eps'... Converting to `/home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-1.pdf'... Success: compilation successfully completed Converting to PNG... Success: compilation successfully completed Writing /home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-systems.texi... Writing /home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-systems.tex... Writing /home/james/lilypond-git/build/out/lybook-db/05/lily-f58ad554-systems.count... Layout output to `/home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-1.eps'... Success: compilation successfully completed Converting to `/home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-1.pdf'... Writing /home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-systems.texi... Writing /home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-systems.tex... Writing /home/james/lilypond-git/build/out/lybook-db/fa/lily-a6ab8ae4-systems.count... Success: compilation successfully completed make[4]: Leaving directory `/home/james/lilypond-git/build/input/regression/lilypond-book' make[3]: *** [WWW-1] Error 2 make[3]: Leaving directory `/home/james/lilypond-git/build/input/regression' make[2]: *** [WWW-1] Error 2 make[2]: Leaving directory `/home/james/lilypond-git/build/input' make[1]: *** [WWW-1] Error 2 make[1]: Leaving directory `/home/james/lilypond-git/build' make: *** [doc-stage-1] Error 2 james@jameslilydev2:~/lilypond-git/build$ --snip-- Hope this helps. james -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: somebody needs to run staging before 29 Jan
David, On 29 January 2012 08:48, David Kastrup d...@gnu.org wrote: James pkx1...@gmail.com writes: --snip-- james@jameslilydev2:~/Desktop/patchy$ ./run-lilypond-staging.sh remote: Counting objects: 83, done. remote: Compressing objects: 100% (57/57), done. remote: Total 57 (delta 45), reused 0 (delta 0) Unpacking objects: 100% (57/57), done. From ssh://git.sv.gnu.org/srv/git/lilypond 39f5057..5a61803 master - origin/master ad3a9e6..8019ff7 staging - origin/staging From ssh://git.sv.gnu.org/srv/git/lilypond * [new tag] release/2.15.27-1 - release/2.15.27-1 Branch test-master-lock set up to track remote branch master from origin. Branch test-staging set up to track remote branch staging from origin. Initialized empty Git repository in /home/james/Desktop/patchy/lilypond-autobuild/.git/ fatal: attempt to fetch/clone from a shallow repository fatal: The remote end hung up unexpectedly Begin LilyPond compile, commit: 39f50579ff91fdca06acd52a9392ab2874f4723b and I don't know where I need to look from here. Run git fetch --depth=100 in your original repository. That should convert it from a shallow repository to a full one. Thanks, I know that Janek and co are doing more work on Patchy so I haven't run it since, however this may be something useful him. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Plans for changing chord repeat implementations
David, On 29 January 2012 02:26, David Kastrup d...@gnu.org wrote: Nicolas Sceaux nicolas.sce...@gmail.com writes: Le 26 janv. 2012 à 11:00, David Kastrup a écrit : The bad news is that absolute pitch friends would have to call the \q function (any better name for it?) explicitly. Since q is an input convenience, and relative pitch is also an input convenience, I don't think that there would be much of an affected user base. I do use absolute pitch mode, together with the q shortcut, so the affected user base is non-nil. URL:http://codereview.appspot.com/5595043 What would be the impact of your solution on this kind of code? Is it just about adding e.g. \q before the block? The user impact is now down to nil. There is no longer any relation of the implementation to \relative. Since you don't need to call it manually except for special considerations (like letting it retain articulations in some passage), \q is now called \chordRepeats. I don't think that there are nightmarish corners in the implementation and behavior any more. So we need to make any tweaks to the NR since ...There is no longer any relation of the implementation to \relative... http://lilypond.org/doc/v2.14/Documentation/notation/single-voice#chord-repetition an @warning or @knownissue? Regards -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: @rlsrnamed{Name,Translation} translates also the name in the URI
Hello,
On 30 January 2012 21:27, Ralph Palmer ralphbugl...@gmail.com wrote:
On Sun, Jan 29, 2012 at 9:38 AM, Federico Bruni fedel...@gmail.com wrote:
Got no answers on -devel, so I forward here (probably more appropriate
place).
Thanks,
Federico
Il 05/01/2012 13:44, Federico Bruni ha scritto:
Issue 1721 reported that @rlsr{Name} keeps the text in english but
translates the link in the translated manuals (no idea where the
translation comes from).
So it recommends to use @rlsrnamed{Name,Translation} instead.
But it looks like @rlsrnamed is affected by the same bug.
Looking through the log file of make doc I've found a lot of errors like
this:
WARNING: Unable to find node 'Hauteurs' in book snippets.
(look at NR 1.1, you'll find a lot of these broken links)
In general, go to the french NR and search for Morceaux choisis ::
you'll see that most of the links are broken.
There are some exceptions, for example this works:
http://lilypond.org/doc/v2.15/Documentation/notation/piano.fr.html
(Claviers link down on the page)
The syntax used is the same: @rlsrnamed{Name,Translation}.
Putting a space after the comma makes any difference.
I can't understand the reason of this weird behaviour.
Can you please explain what's happening?
Thanks,
Federico
Greetings, Federico and list members -
This has been submitted as issue 2266 :
http://code.google.com/p/lilypond/issues/detail?id=2266
Ralph
So where does this leave
http://code.google.com/p/lilypond/issues/detail?id=1721?
Should we merge the two into this?
--
--
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
hello, On 31 January 2012 11:39, Phil Holmes em...@philholmes.net wrote: OK - I've now successfully run test-patches. It downloads and tests the patch associated with issue 2263 (and tests clean). However, there only appears to be a single patch in staging, and that's Carl's fix for 2256. Any idea why it's testing 2263 instead? Not sure why 'instead', but 2263 is the only current patch-new Tracker issue. Listed. http://code.google.com/p/lilypond/issues/list?can=2q=Patch%3Dnew+sort=patchcolspec=ID+Type+Status+Stars+Owner+Patch+Needs+Summaryx=typecells=tiles -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Patchy thread
Hello, On 31 January 2012 14:05, Phil Holmes m...@philholmes.net wrote: - Original Message - From: Graham Percival gra...@percival-music.ca To: Phil Holmes m...@philholmes.net Cc: David Kastrup d...@gnu.org; lilypond-devel@gnu.org Sent: Tuesday, January 31, 2012 1:56 PM Subject: Re: New Patchy thread On Tue, Jan 31, 2012 at 01:47:52PM -, Phil Holmes wrote: There you go. That seemed to work. Yep, looks good. I assume all I need to do is run patchy-staging daily? Yes and no. Running it daily would be great. Running it every 12 hours might be nicer, although maybe you could alternate with James or Reinhold? I'll see how we go. It might be a breakfast and tea job. Another thing to consider is setting up a cronjob. Instead of running it manually, if your computer is always on, it'll just do its thing by itself. Great for 4am in the morning! Can't afford the electric! Might see if I can work out how to wake the computer, run patchy, and go back to sleep. Don't think I could run it at night though - my study's next door to the bedroom and the fans would probably wake us up Well once I get some nice 1, 2, 3 instructions I can run patchy 24/7. I've had to refocus on outstanding Doc tracker issues and Patchy seems to have moved on since two weeks back. Frankly I need the heat in my study ;) -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Staging-Master
Hello, On 2 February 2012 17:11, Phil Holmes m...@philholmes.net wrote: - Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net I believe James indicated his big machine was on 24x7 - hence my instructions if he has some time to look at this. I did glance at them, I've not had a chance to sit down and focus on patchy this week. I'll have more time on the weekend. So if you can bear with me until then I'd appreciate it. Regards -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Unbound variable GUILE error when no whitespace before closing brace
Hello,
Just investigating some old Tracker issues I came across that
\new Staff \with { \override StaffSymbol #'staff-space = #0.9 }
\relative {
\times 2/3 { d16[ d16 d16] }
}
compiles
but
\new Staff \with { \override StaffSymbol #'staff-space = #0.9}
\relative {
\times 2/3 { d16[ d16 d16] }
}
Doesn't.
--snip--
GNU LilyPond 2.14.1
Processing `test.ly'
Parsing...
test.ly:14:58: error: GUILE signaled an error for the expression beginning here
\new Staff \with { \override StaffSymbol #'staff-space = #
0.9}
Unbound variable: 0.9}
test.ly:15:1: error: syntax error, unexpected \relative
etc.
--snip-
Note the lack of white space after the '#0.9'
This occurs on 2.14.1 and 2.15.28.
I guess I've been strict with my spacing or never had braces that
close to an override to notice this before.
I assume this is expected if not nice behaviour. I'm curious only
because I am wondering how a '}' would be a variable and why it isn't
ignored or just signalled (if that is the right term) as a close of
the previous open brace?
Regards
--
--
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Unbound variable GUILE error when no whitespace before closing brace
Hello, On 5 February 2012 07:30, David Kastrup d...@gnu.org wrote: ... The variable is not } but 0.9} instead. Anything that can't be parsed as a constant in Scheme is a variable. This has nothing to do with Lilypond: dak@lola:/usr/local/tmp/lilypond$ guile guile 0.9} ERROR: Unbound variable: 0.9} ABORT: (unbound-variable) guile dak@lola:/usr/local/tmp/lilypond$ You could likely say #(define 0.9} 0.9) and have the above work except for the missing closing brace. There is absolutely nothing that LilyPond could, or even _should_ be trying to fix here. Scheme is Scheme and outside of LilyPond's responsibility regarding syntax and semantics. Thanks, I have no problem with that, it's just a case of 'If I made that mistake then someone else sure will', and wanted to make sure I understood why and if we need to warn users in the doc. We already do :) from the LM 'However, whitespace is required to separate many syntactical elements from others. In other words, whitespace can always be added, but not always eliminated. Since missing whitespace can give rise to strange errors, it is advisable to always insert whitespace before and after every syntactic element, for example, before and after every curly brace.' Hooray! James -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: the word LilyPond
Francisco,
On 9 February 2012 11:45, Francisco Vila paconet@gmail.com wrote:
2012/2/9 Martin Tarenskeen m.tarensk...@zonnet.nl:
Hi,
Everyone who knows a bit about TeX/LaTeX knows what the result looks like
when you use \LaTeX or \TeX in your source text.
Wouldn't it be nice to have something like that for the word LilyPond ? A
standard way to display LilyPond in documents and for example in the
default lilypond tagline ?
I personally would not choose something fancy like (La)TeX uses.
This is my proposal (I did it just for fun a while ago)
lilypond = \markup {
\raise #0.4 \epsfile #X #4 #schematic-lilypond-logo.eps
\epsfile #X #10 #lilypond-logo-fvila-G.eps
%\raise #1.7 {\tiny (.org)}
}
{ c' }
\lilypond
%%END
Files attached.
I like the lilypad and flowers 'icon', but with the typography (and
maybe it's just me) all I can see are 'buttocks'
;)
--
--
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Calling all Londoners
Hmm,.,., On 9 February 2012 17:54, m...@apollinemike.com m...@apollinemike.com wrote: Hey all, On Monday, I'll be crossing the channel to the land where everything's called pudding and people drive on the wrong side of the road. I'll be in London for a couple days for a gig. Are any of you in the area? If so, it'd be great to meet up for coffee! Maybe, but I might be busy 'rolling out my barrel', 'repairing my pearly coat' or 'warming up my beer'. London is a 'big' place Mike and there are 24 hours in a day. Anywhere specific? -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: APIs, hooks, servers and realtime integration
Steve, On 28 February 2012 08:08, Steve Bennett stev...@gmail.com wrote: Hi all, I'm exploring possibilities for a web-based music creation and manipulation tool, and considering LilyPond for rendering the music (is there an alternative? :)). From what I can see in the documentation, it's designed very much as a command line tool, intended to be driven directly by users. Whereas I'm looking for a way to embed it in a web application, and not pay the overhead of loading libraries, parsing and processing entire scores when only small bits change, etc. A search of the archives shows that this question comes up periodically in various forms (a LilyPond server? an API? incremental rendering?), going back to 2005 - but I haven't stumbled on anything much beyond proof of concept. There's Wikitex, but MediaWiki isn't much help to me, and the Wikitex repository and mailing lists (as linked from http://wikitex.org/) seem to be offline. The application will probably be based in Django, so Python hooks would be especially useful. I'd be interested in ways of embedding LilyPond, or running a server that can maintain a bit of state to provide quick response. Any suggestions? Thoughts? Places to look? Other people to ask? :) See thread. http://lists.gnu.org/archive/html/lilypond-user/2012-02/msg2.html Trevor Dixon has recently written a nice web-based app. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: tabloid papersize
hello, On 29 February 2012 08:18, Martin Tarenskeen m.tarensk...@zonnet.nl wrote: Hi, In NR 4.1.2 I read: Common paper sizes are available, including a4, letter, legal, and 11x17 (also known as tabloid). It is known, but lilypond does not allow to use it! #(set-default-paper-size tabloid) It's quite easy (even for me) to add this line: (tabloid . (cons (* 11.0 in) (* 17.0 in))) to the list in paper.scm, as an alias for 11x17, which should also stay. If this is ok, can someone add this in a next Lilypond release ? Added as http://code.google.com/p/lilypond/issues/detail?id=2365 -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: regular patchy staging
Hello, 2012/3/2 Janek Warchoł janek.lilyp...@gmail.com: On Sat, Mar 3, 2012 at 12:01 AM, Graham Percival gra...@percival-music.ca wrote: Any advance on having a regular patchy staging compile? like, every 6 hours or something? Currently it's David who is running Patchy (i am amazed by his involvement), and he lacks processing power to do this more often. I think Patchy could be improved a bit to be more user-friendly (that's just my personal opinion), thus allowing James (for example) to run it more easily. I want to get back to work on Patchy, but i'm totally buried under GSoC and other things; i cannot magically multiply my time despite my sincere wishes to the contrary :( I am back from my break (and the internet connection is much better if still not great - tops out at 300kb/s which is ok) and have been going through the emails that had come in the last week or so, I'm just about caught up and have done a few doc tracker items to boot, and have been trying to get patchy working following the instructions in the CG - they are still a bit vague but we can build on that. I'd saw that David and Graham and (i think) Phil and Janek (?) had been running patchy so figured it was now covered and had been trying to broaden my knowledge elsewhere (for example working out how to update LilyDev - I see a few requests in that area), but if there is still a need for me to run patchy - if only to take the load off - I'll refocus on that. I still have some fundamental questions about the scripts. Patchy actually seems to be two things not one and I am still unclear on this aspect. There is a 'script' that checks Patch-new against current master and there is a 'script' that merges staging with master. Is it required (desired) to run both aspects for me or should I just be doing one of them? It isn't clear from the files I download which does what and which I don't need if I only want to do one or the other. I am working this weekend but will have some free time in the evening. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: unexpected accidental following cadenza
Hello,
On 3 March 2012 08:11, David Bobroff bobr...@centrum.is wrote:
I got a surprise when a cancelling accidental was printed at the beginning
of a measure. This happened following a cadenza. Short example below:
%%%
\version 2.14.2
\relative c'
{
\key c \major
\cadenzaOn
fis4 g a b
\cadenzaOff
\bar |
f
}
%%%
Is this a bug?
Could be..
If you use
%%%
\version 2.14.2
\relative c'
{
\key c \major
\cadenzaOn
fis4 g a
b
\cadenzaOff
\bar |
fis fis fis fis
f f f f
}
%%%
Then the natural symbol doesn't occur in the *next* measure.
--
--
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: regular patchy staging
Hello, On 3 March 2012 09:03, David Kastrup d...@gnu.org wrote: James pkx1...@gmail.com writes: I'd saw that David and Graham and (i think) Phil and Janek (?) had been running patchy so figured it was now covered There is staging-patchy. It does not require manual work, just processing power, but lots of that. It is not bothered if people run it in parallel (the worst that happens is that cycles are wasted). I still run it occasionally, and it is rather a holdup on my setup. Then there is test-patchy. It takes less processing power, but the results need to be evaluated manually and an appropriate comment made. It does not matter if people run it in parallel, but it is a bit of a nuisance if the manual commenting overlaps. staging-patchy and test-patchy currently use the same testing directory (why?), so it will lead to problems if both are run on the same machine at the same time. I still have some fundamental questions about the scripts. Patchy actually seems to be two things not one and I am still unclear on this aspect. There is a 'script' that checks Patch-new against current master and there is a 'script' that merges staging with master. Is it required (desired) to run both aspects for me or should I just be doing one of them? lilypond-patchy-staging (?) is the more important one since it takes more processing power and less manual intervention. OK thanks, I'll focus on that one. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: regular patchy staging
Graham, 2012/3/3 Graham Percival gra...@percival-music.ca: On Sat, Mar 03, 2012 at 09:56:33AM +0100, Janek Warchoł wrote: On Sat, Mar 3, 2012 at 9:16 AM, James pkx1...@gmail.com wrote: I still have some fundamental questions about the scripts. Have you read http://lilypond.org/doc/v2.15/Documentation/contributor/patchy ? Yes. GrahamDavid, when i said that i'd like to make Patchy more user-friendly i meant to make it so straightforward that these questions wouldn't have been asked. Have you read http://lilypond.org/doc/v2.15/Documentation/contributor/patchy ? Janek, tell me exactly which step in that process is unclear. Making vague claims of it should be more user-friendly does not help. I guess in my case it just wasn't clear to me if we can run one without the other 'all the time' (i.e. as I have now found out what Phil does), and that the two scripts were not dependent (i.e. I can only run one when the other has run or I should run the other when the other has run). Phil and David have just made that more clearer to me. Also should I be running both or would it better to just run one and (for instance) let someone else 'merge'. That was all. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Patchy up and running now
Hello, Looks like I am (just about) good to go. --snip-- - Forwarded message -- From: pkx1...@gmail.com Date: 4 March 2012 07:01 Subject: Patchy email To: pkx1...@gmail.com Cc: pkx1...@gmail.com Begin LilyPond compile, commit: acb4ce2a0927ae1899752c991d1c843f5b01196e Merged staging, now at: acb4ce2a0927ae1899752c991d1c843f5b01196e Success: ./autogen.sh --noconfigure Success: ../configure --disable-optimising Success: nice make clean -j7 CPU_COUNT=7 Success: nice make -j7 CPU_COUNT=7 Success: nice make test -j7 CPU_COUNT=7 Success: nice make doc -j7 CPU_COUNT=7 --snip-- I don't really understand why I still had the same issues as I had before - git would complain about shallow repositories (I did look it up but it didn't shed any light) so I simply rm -rf'ed my lilypond-git and cloned down another one and it all worked fine. oh well. Anyway, I'm back at home this evening and will have a few more test runs (with cron just to make sure I can leave it unattended) and then by Monday I should be running 'lilypond-patchy-staging.py' as often as people want me to. Any specific schedule? James -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy up and running now
David, On 4 March 2012 08:20, David Kastrup d...@gnu.org wrote: James pkx1...@gmail.com writes: I don't really understand why I still had the same issues as I had before - git would complain about shallow repositories (I did look it up but it didn't shed any light) I answered your respective last time on the list with a recipe of how to unshallow a clone. Yes you did --snip-- git fetch --depth=100 in your original repository. That should convert it from a shallow repository to a full one. --snip-- That didn't work :( so I simply rm -rf'ed my lilypond-git and cloned down another one and it all worked fine. That's something I would avoid doing: you not just lose all local branches, but also your reflog in that manner. Any work that you did in the repository locally is lost then. The reflog is handy for reviving things which you removed because of an error or erroneous assumptions. In any case, the deed is done now. It's ok. I don't work with my own branches ever. I make a patch and save the patch, then I do a hard reset (with lilygit) and make the next patch, save the next patch etc then apply patch X when I need to change it or push it. There are many cons to that method I know :) but the pros for me outweigh them. My patches tend to touch files that no one else touches :( so it's rare I ever end up with a patch that cannot be applied at a later date. So I didn't lose any work. Anyway, I'm back at home this evening and will have a few more test runs (with cron just to make sure I can leave it unattended) and then by Monday I should be running 'lilypond-patchy-staging.py' as often as people want me to. Any specific schedule? Don't schedule it to run at the same times as Phil since then we are more likely to get complaints from the jobs (and it is not necessary). I'll probably try making the push procedure aware of this particular situation of partial overlap at some point of time, just to make the automated procedure complain less if many people are being helpful. But it is not like anything can go wrong in that manner. I'm not sure if Phil wants to leave his machine running during his day (I know it's too noisy during the evening) but I'll let him tell me when he wants to schedule his. I have said I get intermittent loss of internet so him and I running in tandem or Phil filling in the odd gap in my schedule would make my lack of internet less problematic. Not saying I am down that much, but very occasionally it has been for a whole day. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: templates for writing mysicological book
Hello, On 4 March 2012 10:07, vedran.vu...@gnulinuxcentar.org wrote: Hello, ... Do you know is Lilypond plugin for OpenOffice updated regularly. I could not find decently new versions for Libre Office. You mean this: http://ooolilypond.sourceforge.net/ ? I don't think so. I'll cc the development list to see if anyone has any comment or suggestions. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy up and running now
Phil, On 4 March 2012 10:55, Phil Holmes m...@philholmes.net wrote: - Original Message - From: James pkx1...@gmail.com I'm not sure if Phil wants to leave his machine running during his day (I know it's too noisy during the evening) but I'll let him tell me when he wants to schedule his. I have said I get intermittent loss of internet so him and I running in tandem or Phil filling in the odd gap in my schedule would make my lack of internet less problematic. Not saying I am down that much, but very occasionally it has been for a whole day. -- James I'd suggest we go with a worker standby system - i.e. I'll assume you're running patchy-staging now, and won't run it unless you mail me if you lose internet... Oh. Well. I'll run it if I see master is well out of date - say 18 hours or so. OK, but for now until I let you know (hopefully tonight or monday night) keep it running as normal on your side. I just want to make sure that it all works as expected. Regards -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy up and running now
Hello, On 4 March 2012 11:10, Graham Percival gra...@percival-music.ca wrote: On Sun, Mar 04, 2012 at 08:10:59AM +, James wrote: Anyway, I'm back at home this evening and will have a few more test runs (with cron just to make sure I can leave it unattended) and then by Monday I should be running 'lilypond-patchy-staging.py' as often as people want me to. Any specific schedule? I suggest either every 12 hours or every 6 hours. If we had other systems running cron then it might be nice to spread the load by staggering the runs, but it sounds like Phil only runs it manually after booting that machine. Sounds good. I'll aim for the 00:00/06:00/12:00/18:00 schedule. If Phil doesn't mind I can add him as a cc on the email so he can just check that over his morning cornflakes (when I'll either be in bed or at work depending) and see if he got one or not. Then he'll know if it was X hours since an email or X hours since the merge failed. Then decide if he wants to run it manually to catch up or perhaps if someone does break something and then fix it in the 6 hour window he can merge it himself? It would be nice if somebody else with a fast computer could set it up as well, just so that more people know how to do it... but it seems like the CG is relatively good at explaining patchy staging-merge, so I'm not too fussed about that now. Once I have it up and running I'll take a look at the patchy instructions as I'd like to add some finer points (for n00bs like me - i.e. how NOT to send Graham emails every 2 minutes while you struggle to get it working :) and confuse Mr Kastrup at the same time ). -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy up and running now
Hello, On 4 March 2012 11:10, Graham Percival gra...@percival-music.ca wrote: On Sun, Mar 04, 2012 at 08:10:59AM +, James wrote: Anyway, I'm back at home this evening and will have a few more test runs (with cron just to make sure I can leave it unattended) and then by Monday I should be running 'lilypond-patchy-staging.py' as often as people want me to. Any specific schedule? I suggest either every 12 hours or every 6 hours. If we had other systems running cron then it might be nice to spread the load by staggering the runs, but it sounds like Phil only runs it manually after booting that machine. It would be nice if somebody else with a fast computer could set it up as well, just so that more people know how to do it... but it seems like the CG is relatively good at explaining patchy staging-merge, so I'm not too fussed about that now. I cant seem to get cron jobs to run on my LilyDev - I've done all the cron.allow etc. I was wondering (if anyone knows immediately) if stating the command in cron requires anything special if using two concatenated commands. I.e. I run cd /home/james/lilypond-git python /home/james/patchy/lilypond-patchy-staging.py which works at the CLI but not when I enter that literally in cron. I tried surrounding it in ' but that didn't seem to make any difference. I'll look more on the internet to see (man page wasn't that helpful). Anyway, for now I have a 'while true do patchy then sleep 6 hours done' loop running on my box at home which does the job just as well until I figure why cron isn't working. So I think after tonight you can consider patchy staging running on my machine at home 24 x 7 (internet connection accepted :) ). Phil, can I add you as a cc to patchy in case it all goes wrong and you [don't]get the notification? -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: MacOS X development and support
Hello, On 5 March 2012 07:45, Phil Holmes m...@philholmes.net wrote: - Original Message - From: Graham Percival gra...@percival-music.ca To: Colin Hall colingh...@gmail.com Let's drop Lilypad. It's getting in the way of regular releases. Disagree. Disagree. I'm with Colin. I've already said that I can't see the point of it on Windows: it's a cut-down version of notepad. If it's the same on Mac, I don't see the value. \PointAndClickOn That was a great feature for a 'mac user' like me. While I can run CLI in terminal.app, getting another editor to work with pointAndClick was fruitless and frustrating (at least for 2.12 and 2.13.x when I had my mac). So I'm with Graham on this one. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy up and running now
Hello, On 5 March 2012 09:41, David Kastrup d...@gnu.org wrote: James pkx1...@gmail.com writes: I cant seem to get cron jobs to run on my LilyDev - I've done all the cron.allow etc. I was wondering (if anyone knows immediately) if stating the command in cron requires anything special if using two concatenated commands. I.e. I run cd /home/james/lilypond-git python /home/james/patchy/lilypond-patchy-staging.py which works at the CLI but not when I enter that literally in cron. I tried surrounding it in ' but that didn't seem to make any difference. What is your complete cron line? You are aware that the PATH variable is set to a quite basic path? It was 15 * * * * cd /home/james/lilypond-git python /home/james/patchy/lilypond-patchy-staging.py I intended to leave it for a few hours to see if I got the expected behaviour In the end I hope to use 0 */6 * * * cd /home/james/lilypond-git python /home/james/patchy/lilypond-patchy-staging.py -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy up and running now
Hello, On 5 March 2012 10:32, David Kastrup d...@gnu.org wrote: James pkx1...@gmail.com writes: Hello, On 5 March 2012 09:41, David Kastrup d...@gnu.org wrote: James pkx1...@gmail.com writes: I cant seem to get cron jobs to run on my LilyDev - I've done all the cron.allow etc. I was wondering (if anyone knows immediately) if stating the command in cron requires anything special if using two concatenated commands. I.e. I run cd /home/james/lilypond-git python /home/james/patchy/lilypond-patchy-staging.py which works at the CLI but not when I enter that literally in cron. I tried surrounding it in ' but that didn't seem to make any difference. What is your complete cron line? You are aware that the PATH variable is set to a quite basic path? It was 15 * * * * cd /home/james/lilypond-git python /home/james/patchy/lilypond-patchy-staging.py Hopefully in one line. yes :) Where does it get the LILYPOND_GIT variable? Is it set elsewhere in the cronfile? If not, you need to write something like LILYPOND_GIT=/home/james/lilypond-git python ... instead of just python ... That's set in my .profile or .bashrc - cannot remember off hand - LilyDev has this set and I know I use echo $LILYPOND_GIT it reports back /home/james/lilypond-git. The python scripts also 'complain' if you don't have it set, they check and report back, so again I know from that perspective it all works. Don't waste too much of your own time David, I just wanted to make sure that running two commands in cron didn't need some special 'qualifier' or that I should use ';' instead of '' (although i know the difference). I'll try to figure it out. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patchy up and running now
Francisco On 5 March 2012 10:57, Francisco Vila paconet@gmail.com wrote: 2012/3/5 James pkx1...@gmail.com: What is your complete cron line? You are aware that the PATH variable is set to a quite basic path? It was 15 * * * * cd /home/james/lilypond-git python /home/james/patchy/lilypond-patchy-staging.py I intended to leave it for a few hours to see if I got the expected behaviour In the end I hope to use 0 */6 * * * cd /home/james/lilypond-git python /home/james/patchy/lilypond-patchy-staging.py My humble advice is to put only a script call here. Then the script can do multiple things, echo progress comments, etc. Yes you are probably right. :) -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Ubuntu 12.04 as a LilyDev
Hello,
I've just been seeing if Ubuntu 12.04 is going to cause any
significant problems for the next major LilyDev upgrade.
I had no problems at all.
12.04 is still in beta
1.
https://wiki.ubuntu.com/PrecisePangolin/TechnicalOverview/Beta1#Download_the_Beta_1
This was the image I used
http://ubuntu.virginmedia.com/releases//precise/ubuntu-12.04-beta1-desktop-i386.iso
2. Then after installing as a VM downloaded a further 170mb of Ubuntu
'software updates'
3. Reboot (as prompted) and then following the CG here:
http://lilypond.org/doc/v2.15/Documentation/contributor/requirements-for-compiling-lilypond
sudo apt-get build-dep lilypond
That's about 298mb of more downloads.
4. Extra software that I needed to download
i. dblatex (required for make doc)
ii. autoconf (required for well ./autogen.sh)
iii. git (and gitk if you so wish)
5. Download lilygit-tcl and run it then fill in your name and email
and 'get source'. Wait until that all downloads.
6. when I run ../configure I get:
--snip--
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking Package... LILYPOND
checking builddir... /home/james/lilypond-git/build
checking for stepmake... ../stepmake (${datarootdir}/stepmake not found)
checking for gmake... no
checking for make... make
checking for find... find
checking for tar... tar
checking for bash... /bin/bash
checking for python... python
checking python version... 2.7.2
checking for python... /usr/bin/python
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether compiler understands -pipe... yes
checking for IEEE-conformance compiler flags... none
checking for fc-list... fc-list
checking New Century Schoolbook PFB files...
/usr/share/fonts/type1/gsfonts/c059016l.pfb
/usr/share/fonts/type1/gsfonts/c059036l.pfb
/usr/share/fonts/type1/gsfonts/c059033l.pfb
/usr/share/fonts/type1/gsfonts/c059013l.pfb
checking for python... /usr/bin/python
checking /usr/bin/python version... 2.7.2
checking for /usr/bin/python... /usr/bin/python
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking gcc version... 4.6.3
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking g++ version... 4.6.3
checking options for known g++ tail call bug... -fno-optimize-sibling-calls
checking whether explicit instantiation is needed... no
checking for stl.data () method... yes
checking for ar... ar
checking for ranlib... ranlib
checking for dlopen in -ldl... yes
checking for dlopen... yes
checking for bison... bison -y
checking for bison... bison
checking bison version... 2.5
checking for flex... flex
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking FlexLexer.h usability... yes
checking FlexLexer.h presence... yes
checking for FlexLexer.h... yes
checking for yyFlexLexer.yy_current_buffer... no
checking FlexLexer.h location... /usr/include/FlexLexer.h
checking language... English
checking for gettext in -lintl... no
checking for gettext... yes
checking for msgfmt... msgfmt
checking for mf-nowin... mf-nowin
checking for mpost... mpost
checking for working metafont mode... ljfour
checking for kpsewhich... kpsewhich
checking for guile-config... guile-config
checking guile-config version... 1.8.8
checking guile compile flags... -pthread
checking guile link flags... -pthread -lguile -lltdl
-Wl,-Bsymbolic-functions -lgmp -lcrypt -lm -lltdl
checking libguile.h usability... yes
checking libguile.h presence... yes
checking for libguile.h... yes
checking for scm_boot_guile in -lguile... yes
checking for scm_boot_guile... yes
checking for scm_t_hash_fold_fn... no
checking for scm_t_hash_handle_fn... no
checking for scm_t_subr... no
checking for usable C++ demangler... yes
checking GUILE rational bugfix... ok
checking for python-config... python-config
checking Python.h usability... yes
checking Python.h presence... yes
checking for Python.h... yes
checking for gs... gs
checking for gs... /usr/bin/gs
checking /usr/bin/gs version... 9.05
checking for fontforge... fontforge
checking for fontforge... /usr/bin/fontforge
checking /usr/bin/fontforge version... 20110222
checking
Re: Ubuntu 12.04 as a LilyDev
Hello, 2012/3/6 Janek Warchoł janek.lilyp...@gmail.com: On Tue, Mar 6, 2012 at 8:25 PM, James pkx1...@gmail.com wrote: Hello, I've just been seeing if Ubuntu 12.04 is going to cause any significant problems for the next major LilyDev upgrade. [...] make and make doc work fine (well make doc completes with no errors I haven't actually looked through all the PDFs but the LM looked fine on a quick skim). I'm not going to comment on the Unity interface as I know that is a sore topic for some users, but apart from figuring out how to get an xterm (alt-f2 then type xterm!) it was pretty pain free. It's certainly a smoother experience than 10.04 (if one cares about that subtlety) even in a VM. Compilation times are no quicker/slower it seems, although I haven't 'watched' a make doc for a few months now (I just kick off the command and go and have a life, it's all done when I get back) so I thought it had 'hung' as I am conditioned with my few years of making doc of a constant stream 'matrix like' of screenout put. But this stuttered and stopped so much I really thought something was wrong, Then I realised... Well 'squashed' Mr Phil! :) Anyway, hope this was useful or interesting at the very least. It was! Maybe LilyDev 2.0 should be Ubuntu 12.04. No we have to think about GUB and the fact that 12.04 is still in beta. I think as has been suggested by Graham that we'll do another round on 10.04 with LilyDev 2.5 and then once 12.04 has bedded in a bit then move. I need also to make sure that remastersys (which is what we use to build the ISO) works on 12.04 - I haven't tried that yet. The only thing that concerns me is xterm. Do i understand correctly that it's the only available terminal? No, you understand that that was the only thing I could think to type for a terminal at that moment :) The default one in current LilyDev is much better, has tabs and all eye-candy a terminal can have. Quite. James -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyPond 2.14.2 is in Ubuntu 12.04 software centre
Francisco, On 5 March 2012 23:41, Francisco Vila paconet@gmail.com wrote: 2012/3/5 James pkx1...@gmail.com: Hello, Just in case anyone was interested. Thanks to whoever sorted this out - it used to be 2.11 or even 2.10 not so many months ago. 330.7 MB to download, 905.2 MB when installed? Synaptic says size 4293 kB, download 1535 kB for v 2.12.3-7ubuntu1 in my Ubuntu 11.04 system. Looks very wrong. Or, does that include all of texlive or something? http://packages.ubuntu.com/precise/lilypond and then see http://packages.ubuntu.com/precise/lilypond-doc ? I don't pretend to understand this. Regards -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Ubuntu 12.04 as a LilyDev
Hello 2012/3/6 Francisco Vila paconet@gmail.com: 2012/3/6 Janek Warchoł janek.lilyp...@gmail.com: The only thing that concerns me is xterm. Do i understand correctly that it's the only available terminal? The default one in current LilyDev is much better, has tabs and all eye-candy a terminal can have. What does Ctrl+Alt+T do? ;) Bingo! James -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bad translation merge
David On 7 March 2012 12:58, David Kastrup d...@gnu.org wrote: David Kastrup d...@gnu.org writes: David Kastrup d...@gnu.org writes: Hi, the recent translation merge apparently made some wrong choices when dealing with merge conflicts. Changes in staging have been overwritten in the following files: And that affects a lot more than just translations. I have removed that commit from origin/staging, and we'll have to investigate what happened. Francisco, do you remember the commands you used for merging translation into staging? I'll try repeating this on my own and see whether I can reproduce this. I can reproduce the problems when merging. It would appear that the history of the translation branch got messed up at some point of time in a manner that git can't recognize how to merge properly anymore. I will try to figure out what happened here. Please don't merge the translation branch to staging while I try figuring this out. Ok, the shit hit the fan. Apparently I was not fast enough, and somebody ran the staging-merge on the bad translation merge. Now master is borked. I won't be home until at least another patchy run (scheduled around 18:00 BST) and perhaps the one at midnight - depending when I get back. If it helps Graham (or someone) could disable my account at Savannah to stop patchy being able to push/merge. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bad translation merge
Hello, On 7 March 2012 23:42, David Kastrup d...@gnu.org wrote: David Kastrup d...@gnu.org writes: Well, somebody will likely be me, of course. Sleep is overrated. make check is not all that slow, and I can leave the full doc build to Patchy (assuming he is still on regular duty: there is actually no reason why he shouldn't be). That leaves the translations. Now we can reset them if needed, but I prefer not to do that since rewinding published history is a nuisance, and I don't really want to force the translators to mess more with their repositories than necessary. I suppose I'll push that thing shortly and hope for the best. I pushed both the translation branch as well as staging. The fixed translation branch is merged into staging, but I have not merged staging (hopefully master soon: I think midnight GMT is in 20 minutes, and that should trigger James' patchy) back into translation. Translators should first check that lilypond/translation is in a consistent state (I am doubtful about the committishes). Once it is considered fine, one can merge the (hopefully) new master back, and the two should be reasonably synced again. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel Do you still want me to keep patchy going? I'll pause it for now and if I hear nothing I'll kick it off. Or do you want me to do a make/make doc on something? I'll be around for the next 30 mins or so (until around 00:30 BST). Regards -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bad translation merge
hello, On 8 March 2012 00:04, David Kastrup d...@gnu.org wrote: James pkx1...@gmail.com writes: On 7 March 2012 23:42, David Kastrup d...@gnu.org wrote: David Kastrup d...@gnu.org writes: Well, somebody will likely be me, of course. Sleep is overrated. make check is not all that slow, and I can leave the full doc build to Patchy (assuming he is still on regular duty: there is actually no reason why he shouldn't be). That leaves the translations. Now we can reset them if needed, but I prefer not to do that since rewinding published history is a nuisance, and I don't really want to force the translators to mess more with their repositories than necessary. I suppose I'll push that thing shortly and hope for the best. I pushed both the translation branch as well as staging. The fixed translation branch is merged into staging, but I have not merged staging (hopefully master soon: I think midnight GMT is in 20 minutes, and that should trigger James' patchy) back into translation. Translators should first check that lilypond/translation is in a consistent state (I am doubtful about the committishes). Once it is considered fine, one can merge the (hopefully) new master back, and the two should be reasonably synced again. Do you still want me to keep patchy going? I'll pause it for now and if I hear nothing I'll kick it off. Huh? Why pause? I wrote hopefully master soon. Just let the beast run as scheduled. OK it's off and running. I'll stick about for the next 20 minutes to see what happens. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bad translation merge
Hello, On 8 March 2012 00:04, David Kastrup d...@gnu.org wrote: ... Huh? Why pause? I wrote hopefully master soon. Just let the beast run as scheduled. This is what it reports as it started (just FYI) --snip-- emote: Counting objects: 272, done. remote: Compressing objects: 100% (30/30), done. remote: Total 169 (delta 139), reused 169 (delta 139) Receiving objects: 100% (169/169), 21.91 KiB, done. Resolving deltas: 100% (139/139), completed with 79 local objects. From ssh://git.sv.gnu.org/srv/git/lilypond * [new branch] dev/staging - origin/dev/staging * [new branch] dev/translation - origin/dev/translation 32b9cd0..5697144 lilypond/translation - origin/lilypond/translation 9d1520b..2944a83 staging- origin/staging Branch test-master-lock set up to track remote branch master from origin. Branch test-staging set up to track remote branch staging from origin. Initialized empty Git repository in /home/james/lilypond-git/build/.git/ Updating 9d1520b..2944a83 Fast-forward Documentation/contributor/introduction.itexi |4 +- Documentation/contributor/lsr-work.itexi | 25 +++ Documentation/de/notation/spacing.itely|2 +- Documentation/included/helpus.itexi| 11 +- Documentation/ly-examples/GNUmakefile |2 +- Documentation/notation/rhythms.itely | 30 +++- .../snippets/alternative-bar-numbering.ly |2 +- Documentation/snippets/alternative-breve-note.ly |2 +- ...centering-markup-on-note-heads-automatically.ly | 44 ++--- .../creating-metronome-marks-in-markup-mode.ly |2 +- .../customizing-fretboard-fret-diagrams.ly |6 +- ...ining-an-engraver-in-scheme-ambitus-engraver.ly | 45 ++--- ...play-bracket-with-only-one-staff-in-a-system.ly |2 +- .../snippets/formatting-lyrics-syllables.ly|7 +- Documentation/snippets/glissandi-can-skip-grobs.ly |2 +- Documentation/snippets/hymn-template.ly|1 + .../snippets/lyrics-old-spacing-settings.ly|2 +- Documentation/snippets/nesting-staves.ly |2 +- .../snippets/numbers-as-easy-note-heads.ly | 32 ++-- .../snippets/partcombine-and-autobeamoff.ly|2 + .../snippets/placement-of-right-hand-fingerings.ly |4 +- .../snippets/printing-marks-on-every-staff.ly |2 +- ...etronome-and-rehearsal-marks-below-the-staff.ly |2 +- Documentation/snippets/strict-beat-beaming.ly |2 +- .../snippets/woodwind-diagrams-key-lists.ly|2 +- Documentation/web/community.itexi |6 +- GNUmakefile.in |5 +- input/regression/autobeam-3-4-rules.ly | 24 +++ input/regression/multiple-time-sig-settings.ly |4 +- input/regression/rest-on-nonstandard-staff.ly |5 + lily/book-scheme.cc|4 + lily/parser.yy |2 - lily/rest.cc | 31 ++- ly/engraver-init.ly|7 +- ly/event-listener.ly | 26 ++-- ly/init.ly |2 - ly/music-functions-init.ly |8 +- make/lilypond-book-vars.make |2 +- make/ly-rules.make |2 +- make/midi-rules.make |2 +- ps/music-drawing-routines.ps | 21 ++- scm/auto-beam.scm | 48 - scm/define-context-properties.scm |4 + scm/lily-library.scm | 34 +++- scm/lily.scm |4 +- scm/time-signature-settings.scm| 17 +- scripts/build/mutopia-index.py | 197 stepmake/stepmake/texinfo-rules.make |4 +- 48 files changed, 315 insertions(+), 381 deletions(-) create mode 100644 input/regression/autobeam-3-4-rules.ly delete mode 100644 scripts/build/mutopia-index.py Total 0 (delta 0), reused 0 (delta 0) To /home/james/lilypond-git/ 9d1520b..2944a83 test-master-lock - test-master-lock --snip-- -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Fwd: Patchy email
Boom! All done. -- Forwarded message -- From: pkx1...@gmail.com Date: 8 March 2012 00:29 Subject: Patchy email To: pkx1...@gmail.com Merged staging, now at: 2944a83e59f487894a214769392ce27289accb71 Success: ./autogen.sh --noconfigure Success: ../configure --disable-optimising Success: nice make clean -j7 CPU_COUNT=7 Success: nice make -j7 CPU_COUNT=7 Success: nice make test -j7 CPU_COUNT=7 Success: nice make doc -j7 CPU_COUNT=7 Success: pushed to master --- Next merge in 6 hours. Have a nice day! -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Please stop pushing to the translation branch until further notice
Hello, On 8 March 2012 11:08, David Kastrup d...@gnu.org wrote: ... In any case: I think you should merge (merge!) more often, master to translation, translation to staging. It does not make all that much sense if translations come 2 versions later into master than they have been written. And when things go wrong, they go wrong in smaller portions, and fewer stuff needs to get verified after cleaning up. Is this something 'we' could add easily to patchy? Then I could be doing that as part of what I am doing already? -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: since when LilyPond supports unicode?
Janek, 2012/3/9 Janek Warchoł janek.lilyp...@gmail.com: Hi. i'd like to give precise information on how long Lily supports Unicode. I've searched changes on website, mailing lists and git history, but didn't find the date - can you help? cd $LILYPOND_GIT git grep unicode Just a quick glance shows me we mention 'stuff' in Changes around 2.10.x -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Patchy is trying to merge staging now
Patchy is re-running now. I lost internet connection so it missed the 6pm merge. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [patch] Fix mordents and pralltriller in articulate.ly
Hello, 2012/3/14 Janek Warchoł janek.lilyp...@gmail.com: Should this patch (and the other articulation patch) be put on Rietveld or pushed directly? Janek Does it break 'make'? :P I think this needs to be reviewed just like any other patch should be, why *would* we just push this? Also I saw that a new doc commit was merged this morning by you http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=d11dbf277719c0179c5520154c925839d969a535 I might have missed this but did this have a tracker/patchy test? James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Failed make doc for Patchy
I am not at home but Patchy complained just now. -- Forwarded message -- From: pkx1...@gmail.com Date: 14 March 2012 18:34 Subject: Patchy email Merged staging, now at: c6a925ecd742196979038804b02846faad7f2cc9 Success: ./autogen.sh --noconfigure Success: ../configure --disable-optimising Success: nice make clean -j6 CPU_COUNT=6 Success: nice make -j6 CPU_COUNT=6 Success: nice make test -j6 CPU_COUNT=6 *** FAILED BUILD *** nice make doc -j6 CPU_COUNT=6 Previous good commit: d11dbf277719c0179c5520154c925839d969a535 Current broken commit: c6a925ecd742196979038804b02846faad7f2cc9 -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Failed make doc for Patchy
Hello,
On 14 March 2012 20:04, David Kastrup d...@gnu.org wrote:
Phil Holmes m...@philholmes.net writes:
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Wednesday, March 14, 2012 7:16 PM
Subject: Re: Failed make doc for Patchy
James pkx1...@gmail.com writes:
I am not at home but Patchy complained just now.
Shall I run patchy and check the logfiles?
I've just done it and I get this file that causes the complaints
--snip--
%
% Start cut--pastable-section
%
\paper {
indent = 0\mm
line-width = 160\mm
% offset the left padding, also add 1mm as lilypond creates cropped
% images with a little space on the right
line-width = #(- line-width (* mm 3.00) (* mm 1))
}
\layout {
}
%
% ly snippet:
%
\sourcefilename out-www/voice-2-midi.ly
\sourcefileline 0
% Lily was here -- automatically converted by
/home/james/lilypond-git/scripts/midi2ly.py from out-www/voice-2.midi
\version 2.14.0
\layout {
\context {
\Voice
\remove Note_heads_engraver
\consists Completion_heads_engraver
\remove Rest_engraver
\consists Completion_rest_engraver
}
}
% included from ./out-www/voice-2.header
\header {
texidoc=midi2ly maps two voices nicely on one staff as oiceOne, oiceTwo
options=
}
% end
trackAchannelA = {
% [SEQUENCE_TRACK_NAME] control track
% [TEXT_EVENT] creator:
% [TEXT_EVENT] GNU LilyPond 2.15.34
\time 4/4
\tempo 4 = 60
}
trackA =
\context Voice = voiceA \trackAchannelA
trackBchannelA = {
\set Staff.instrumentName = trackB:voiceA
}
trackBchannelB = {
\set Staff.instrumentName = trackB:voiceB
}
trackBchannelC = \relative c {
\voiceOne
e''4 e e e
| % 2
}
trackBchannelD = \relative c {
\voiceTwo
f' f f f
| % 2
}
trackB =
\context Voice = voiceA \trackBchannelA
\context Voice = voiceB \trackBchannelB
\context Voice = voiceC \trackBchannelC
\context Voice = voiceD \trackBchannelD
\score {
\context Staff=trackB \trackA
\context Staff=trackB \trackB
\layout {}
\midi {}
}
%
% end ly snippet
%
--snip--
--
--
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: font regression build regression
Hello, On 14 March 2012 20:00, Phil Holmes m...@philholmes.net wrote: - Original Message - From: Graham Percival gra...@percival-music.ca To: lilypond-devel@gnu.org Sent: Wednesday, March 14, 2012 7:59 PM Subject: font regression build regression Has anybody else seen a huge slow-down in building fonts? They used to whiz by on my screen in a minute or so, but now it takes about 10 minutes, and more to the point, it involves a massive amount of disk activity. My core2quad desktop couldn't play an mp3 file while building fonts with -j3 ! Might it be building the same font multiple times (with different threads creating and deleting the same temporary files?), or are we generating fonts at twice the resolution of the previous one, or...? It's been a few weeks since I tried building stuff from scratch, which leaves a large window of work on the build system and fonts. Is this with a straight make ? I ran it yesterday and didn't see a slowdown, and I always check the time it takes. I did a make on my 1cpu LilyDev VM (when I am work) on 1GB of memory today and didn't see any significant slow down on a 'make'. It takes about 10 minutes. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: tabloid papersize
Hello, On 29 February 2012 18:05, Neil Thornock neilthorn...@gmail.com wrote: While we're at it, it would be nice to enable ledger (17x11) -- noted in paper.scm but not included for some reason. This and a few other sizes have been added and will be in the next development release - 2.15.34 (I believe). Thanks for taking the time to suggest this. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
Hello,
On 16 March 2012 21:30, Graham Percival gra...@percival-music.ca wrote:
On Fri, Mar 16, 2012 at 05:28:21PM -0400, Julien Rioux wrote:
On 16/03/2012 4:55 PM, Graham Percival wrote:
... although apparently that doesn't include a link to the actual
code. huh.
https://github.com/gperciva/lilypond-extra
No?
http://lilypond.org/doc/v2.15/Documentation/contributor/patchy#Installing-patchy
oh, huh. My eyes skipped over it because it wasn't blue.
Anybody feel like wrapping that in a @uref{} ? If so, please push
directly to staging.
Voila!
committer James Lowe pkx1...@gmail.com
Sat, 17 Mar 2012 16:19:17 + (16:19 +)
commit ddc638764124c27750baf39b4c42f7f6d0061a15
--
--
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: new lilypond-auto mailing list
hello, On 20 March 2012 10:47, Reinhold Kainhofer reinh...@kainhofer.com wrote: On 2012-03-20 00:28, Graham Percival wrote: On Tue, Mar 20, 2012 at 12:11:46AM +0100, David Kastrup wrote: So instead of surprising volunteers by giving them more information than expected we give them less information than expected? Bug squad members shouldn't be reading tracker messages anyway. It's not about bug squad, but about all developers. The comment of the lilypond users to the bug reports are *extremely* important for development. On the other hand, all those hundreds of automated comments to the bug reports are totally unnecessary. The thing is you are damned if you do and you are damned if you don't. I think this auto list is a good idea. Some while complain now that they won't know when a Tracker has been updated from a checkin but only when a user updates the checkin. In that case you can use git-cl to cc the dev list if you so wish for your patch upload. Or devs can use the tracker website instead of just relying on emails - there are filters on this site and they work well, I have a set of bookmarks that list me Patch-new, Patch-review and so on, or they can now subscribe to the auto list. or you can simply add another filter to your email. It may be about the devs in your head, but unless 'someone' creates the trackers (and this includes spotting the bug reported in the first place) the devs have nothing to work on (so to speak). We already know that devs hate the 'admin' :) and the idea of the bug-squad is to make the dev's life easier. It isn't perfect but if anything we should give this a try. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fingering avoidance of accidentals depends on Fingering #'script-priority
Nick
On 19 March 2012 05:19, Nick Payne nick.pa...@internode.on.net wrote:
In a chord with two accidentals, if I set the fingering script-priority to
-99, the fingerings still avoid both accidentals, but if I set it to -100,
each fingering indication is positioned without regard to the accidental on
the other note. Is this related to
https://code.google.com/p/lilypond/issues/detail?id=2182, or soemthing else?
\relative c' {
\set fingeringOrientations = #'(left)
fis-4 dis-21
\override Fingering #'script-priority = #-99
fis-4 dis-2
\override Fingering #'script-priority = #-100
fis-4 dis-2
}
I've updated https://code.google.com/p/lilypond/issues/detail?id=2182
with this new example.
--
--
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: casual contributors (was: patch going unpushed)
Hello On 22 March 2012 23:37, Graham Percival gra...@percival-music.ca wrote: On Fri, Mar 23, 2012 at 08:18:26AM +1100, Peter Chubb wrote: Hi Graham, Graham We don't really have a frog meister, so nobody is taking Graham responsibility for pushing I have another patch waiting, that depends on the first. https://lists.gnu.org/mailman/listinfo/lilypond-devel I've offered to shepherd this new patch. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Add an example implementation of cross-staff stems (issue 5882053)
Hello, On 24 March 2012 08:19, d...@gnu.org wrote: On 2012/03/23 21:46:41, Pavel Roskin wrote: OK, I'll use make-engraver in the next revision. I guess I'll need to strip all Lilypond 2.14 compatibility stuff if this snippet is to be a part of the Lilypond documentation. In LilyPond itself, it makes sense to document the latest version. If people read 2.16 documentation, they can't expect to see stuff that is guaranteed to work under 2.14. It is not uncommon for some new features to be only discernible from regtests. That is not really good. This is the current state for Scheme engravers. It would be good to have some nice examples for Scheme engravers in the documentation. This particular case is, in my opinion, too complex for either documentation or a targeted regtest. It is LSR material, or should become part of LilyPond proper if one can think of a good way. Note that we have snippets in the LilyPond documentation/repository as well: those can use the newest features. That would be the proper place, I think. We still need to get Scheme engravers into the main documentation. We have this http://code.google.com/p/lilypond/issues/detail?id=1995 We could incorporate 'Scheme stuff' via this. As I;ve always said, although I don't understand this from a technical point of view if someone can articulate what they want in text form I can do the texinfo 'stuff' to get it in the doc. I'm not sure if the NR is the correct place as opposed to a new @node (or similar) in Extending or whatever. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: German translation request
Hello
On 25 March 2012 14:10, Phil Holmes em...@philholmes.net wrote:
In Notation/wind.itely, please could the following be changed:
Die Liste aller möglichen Löcher und Einstellungen eines bestimmten
Instruments kann auf der Kommandozeile oder in einer Log-Datei
angezeigt werden, auch wenn man sie nicht in der Notenausgabe anzeigen
lassen kann:
@lilypond[verbatim,quote]
#(print-keys-verbose 'flute)
@end lilypond
So that we lose the lilypond fragment, but instead use an @code{} block for
the print-keys instruction. This has been done for the English and other
languages, and the remaining use in the German manuals produces about 7% of
the un-needed output from make doc.
Thanks.
http://code.google.com/p/lilypond/issues/detail?id=2437
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
Marek, On 23 March 2012 21:42, Marek Klein ma...@gregoriana.sk wrote: 2012/3/23 Graham Percival gra...@percival-music.ca On Fri, Mar 23, 2012 at 10:31:20PM +0100, Marek Klein wrote: I've succeeded in building lilypond. :) test-patches.py says: No new patches to test. What are my next steps? I've just set issue 2216 to Patch-new, so try running it again. Trying issue 2216 Found patch: (2216, '/home/marek/lilypond-patchy/issue5843060_6001.diff', 'AU: Document all options for lilypond -dhelp') Traceback (most recent call last): File test-patches.py, line 16, in module main(issues_id) File test-patches.py, line 12, in main patchy.do_check(issues) File /home/marek/lilypond-patchy/projecthosting_patches.py, line 213, in do_check compile_lilypond_test.main(patches) File /home/marek/lilypond-patchy/compile_lilypond_test.py, line 282, in main autoCompile.prep_for_rietveld() File /home/marek/lilypond-patchy/compile_lilypond_test.py, line 140, in prep_for_rietveld self.update_git() File /home/marek/lilypond-patchy/compile_lilypond_test.py, line 112, in update_git run(git fetch) File /home/marek/lilypond-patchy/compile_lilypond_test.py, line 45, in run raise Exception(Command '%s' returned non-zero exit status %d\n%s % (cmd, returncode, stderr.strip())) Exception: Command 'git fetch' returned non-zero exit status 128 error: insufficient permission for adding an object to repository database .git/objects fatal: failed to write object fatal: unpack-objects failed Did you get it working yet? It seems that permissions to your $LILYPOND_GIT location or who you are running the script as are not allowed to 'git fetch' and pull down any changes from the current code to apply the patch to then check it. Either you need to change the permissions somewhere (probably unlikely) or you need to edit the files further to make sure that the scripts are trying to 'fetch' the most up to date branch to the correct place. If you can let us know if you 1. Edited any of the files before you tried to run the scripts 2. If your %LILYPOND_GIT location is set - if you use LilyDev it should already be set for you. Regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: volunteer for patchy new-patches
Marek, On 27 March 2012 18:48, Marek Klein ma...@gregoriana.sk wrote: Hi, 2012/3/23 Graham Percival gra...@percival-music.ca Well, you need to figure out why git fetch in your $LILYPOND_GIT repository fails. git fetch works now... I need som new patch for play with... Marek I reset one of mine on the countdown http://code.google.com/p/lilypond/issues/detail?id=2216 Try that. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: how to handle big attachments to bugreports?
Janek, 2012/3/27 Janek Warchoł janek.lilyp...@gmail.com: Hi, i have a multi-issue bug report almost done, and it contains about 5 MB of examples (i've already cut it down). I remember that we have little space on google tracker, how shall i handle these files? I don't have my webserver and i don't like the idea of putting them on some hosting website, because they'll disappear after some time. Can they be hosted on LilyNet or something? Use nabble. I did for all my reg tests I did before we went 'patchy'. I'd link to that from Rietveld for users to look at. Reg tests can get large, For example http://lilypond-stuff.1065243.n5.nabble.com/Tracker-issue-2051-24-November-td4986583.html Might be easier. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: casual contributors
Hello, 2012/3/23 Janek Warchoł janek.lilyp...@gmail.com: On Fri, Mar 23, 2012 at 8:06 PM, David Kastrup d...@gnu.org wrote: What impressed you most about the LilyPond code base? No comment. But I really want to know! I just told you. LOL!! That's a quote-of-the-month! Janek :D Having just read his thread I was hoping more for .. jetzt Runter von meinem Rasen! ;) James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LSR is now on 2.14
Hello, On 30 March 2012 02:24, Graham Percival gra...@percival-music.ca wrote: ... Well, currently I can't self-compile LilyPond or prepare a formal patch or sth else in this direction. Seems I have to learn a lot. ;) Yep. To warn you: at the moment the quick start section of the CG is broken; following its instructions will give you neither a quick nor painless start. Your options are: 1) go through the painful process of figuring out which parts are still valid and which are not. Without a mentor, this will be especially painful. 2) wait for lilydev to be updated (ETA: 6 weeks) and somebody to fix up at least the short quick start section (ETA: 1 month after lilydev is updated). 3) ask/wait for somebody else to handle the LSR import. Unfortunately there is no magic wand that will let us offer you an option other than those three. (unless I've forgotten about something, which is possible given my mental state these days. James: I have not forgotten about your recent work on lilydev, but I stand behind my pessimistic estimate) I've updated LilyDev and been working with it this week testing the basics - it makes the code and the doc. I've given Mike a copy of the iso (as he was the only one I knew who used LilyDev in anger) and I FTP'd the iso to Phil's website last night. As far as I know, this is good to go. Thomas the ISO is a 32 bit, 10.04 version of Ubuntu that can be installed directly on hardware or, as I do, used in a Virtual Machine on any x86 based hardware (i.e. Virtual Box for Windows/Mac/Linux). I've compiled the binary using as little as 750mb of RAM with a single CPU - you'll need about 10GB of disk space (give or take), but if you ever wanted to make the whole doc you'd need more and 1 CPU with small amounts of RAM would take a while to compile all the doc. For LSR you don't need this, obviously. It doesn't do GUB, but it has everything else asked for on the tracker. I can take a look at the quick start over the weekend, but after the iso is downloaded (and I am no programmer) I can be installed with Virtual Box and have a compiled binary - of the latest dev version - in less than an hour (assuming you have a relatively fast internet to download the code) of which 80% of that is letting the computer just run. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LSR is now on 2.14
Phil, I use LilyDev quite a bit - a slightly out of date version. The only machine for which this is not true is the Ubuntu 64-bit real machine I use for build. My PC VM is lilydev, as is my GUB VM on the big build box. Oh good. I thought you only used a phys machine. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Corrected style of comments (issue 5862052)
Hello, 2012/3/31 Janek Warchoł janek.lilyp...@gmail.com: On Sat, Mar 31, 2012 at 6:13 PM, milimet...@gmail.com wrote: I'm sorry for that, but the next bunch of corrections are in a separate issue: http://codereview.appspot.com/5975054 It seems that following the procedure from http://lilypond.org/doc/v2.15/Documentation/contributor/commits-and-patches#uploading-a-patch-for-review does not make git-cl ask for the issue number. Instead it creates a new one. How to change that? Always call 'git cl issue' before 'git cl upload'? The information about Rietveld issue is stored in your git config, in the properties of the branch you used when you uploaded first. If you upload new patch revision from a new branch, the script doesn't know what rietveld number is because it doesn't see it in branch properties. It's a good practice to use one branch for your fix. I find that using 'git-cl issue 0' helps to 'reset' any doubts abuot what git-cl thinks it has currently. I use a VM with Lilydev and have a number of patches on the go, so forget which is which, so just reset git-cl and then either let git-cl create my new issue number or I find my rietveld issue and then run git-cl issue where is the rietveld number. Then I know I am good to go. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Fwd: Staging/Master Merge - James' Patchy
I might have some internet issues at home. Patchy hasn't pushed since midday or emailed until now. I cannot remember what the message is if it 'fails' to connect to the internet - I think it posts this generic message. I'll check when I get home, there are no commits I can see in master or staging since yesterday. So this is probably just an internet connection glitch. James -- Forwarded message -- From: lilypond.patchy.jl...@gmail.com Date: 3 April 2012 17:31 Subject: Staging/Master Merge - James' Patchy To: lilypond-a...@gnu.org, pkx1...@gmail.com Cc: pkx1...@gmail.com *** FAILED STEP *** merge from staging maybe somebody pushed a commit directly to master? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: rall. and accel stopped working in articulate. (issue 5927044)
Peter, On 4 April 2012 00:21, pe...@chubb.wattle.id.au wrote: pkx166h == pkx166h pkx1...@gmail.com writes: pkx166h Peter, this has passed our 'countdown' review, if you don't pkx166h yet have push access you can email me a git-formatted patch pkx166h and I can push it for you. OK here it is. Thanks, pushed as author Peter Chubb peter.ch...@nicta.com.au Wed, 14 Mar 2012 22:48:52 + (09:48 +1100) committer James Lowe pkx1...@gmail.com Wed, 4 Apr 2012 08:12:52 + (09:12 +0100) commit 42ca3ff037c8ca7a7c65bf3b1423dfcb5d974d2e Can you close your Rietveld issue? Many thanks james ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch push announcements
Colin, On 4 April 2012 04:20, Colin Campbell c...@shaw.ca wrote: When a countdown completes, I mark the tracker item patch-push and Google dutifully sends the resulting email to lilypond-auto, where it formerly went to -devel. I wonder if the owners are getting the notification, and if so, how we handle those tracker items which do not have an owner? It will take some getting used to, but perhaps this will now 'coerce' all trackers with a patch to have an owner. If I notice one - Mike S for instance - not picking on him especially but in the olden days when he was 'quick-patch-McMike', and when I was checking patches manually, I'd fix the tracker myself as I could see who was the Rietveld owner. That is a bit tedious. I've been pushing patches (Alberto, Pavel, Peter) for those trackers that don't have a dev who has push access, and as part of my bug shift (on Saturdays if I remember) because I am aware of this, I'll skim 'push' labeled trackers or 'review' labeled trackers and assign them owners if I can. Not saying that should be another bug squad duty, but that's what I do when I remember. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LSR is now on 2.14
Hello, On 4 April 2012 16:07, Phil Holmes m...@philholmes.net wrote: - Original Message - From: Thomas Morley thomasmorle...@googlemail.com To: Graham Percival gra...@percival-music.ca Ok, I checked it. Only the following 37 files have to be added manually (the others are updates of existing LSR-files) I've updated the LSR with all the new files - i.e. I've added them to docs and approved them. We should know 2 hours from now when Patchy does it's thing and tries to merge staging and master. :) James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: musicxml2ly
Hello, On 8 April 2012 17:47, Martin Tarenskeen m.tarensk...@zonnet.nl wrote: ... Or are many problems already known? http://code.google.com/p/lilypond/issues/list?can=2q=musicxmlsort=prioritycolspec=IDx=typey=prioritymode=gridcells=tiles There is also this recent - seemingly unfinished patch http://codereview.appspot.com/5697059/ And see http://lists.gnu.org/archive/html/lilypond-devel/2011-12/msg00025.html http://lists.gnu.org/archive/html/lilypond-user/2011-11/msg00280.html This will give you an idea of the current issues and the effort still required. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Staging/Master Merge - James' Patchy
Hello, On 8 April 2012 18:11, Phil Holmes m...@philholmes.net wrote: lilypond.patchy.jl...@gmail.com wrote in message news:4f81c580.c507b40a.6878.7...@mx.google.com... Begin LilyPond compile, commit: eebdf598862812edf142f1c52a727c962bf26465 Merged staging, now at: e045a8a796ea14ac04838af850e89da3a9343bb0 Success: ./autogen.sh --noconfigure Success: ../configure --disable-optimising Success: nice make clean -j6 CPU_COUNT=6 *** FAILED BUILD *** nice make -j6 CPU_COUNT=6 Previous good commit: 18cc52e04834f7eaec4d41cf2783767b0e764d03 Current broken commit: e045a8a796ea14ac04838af850e89da3a9343bb0 Begin LilyPond compile, commit: 1b473723a8acf07a58f44561068fed212e5bcd98 Merged staging, now at: e045a8a796ea14ac04838af850e89da3a9343bb0 Success: ./autogen.sh --noconfigure Success: ../configure --disable-optimising Success: nice make clean -j6 CPU_COUNT=6 *** FAILED BUILD *** nice make -j6 CPU_COUNT=6 Previous good commit: Current broken commit: e045a8a796ea14ac04838af850e89da3a9343bb0 This is my LSR update. It was OK on my machine, but I'll run patchy myself and see what's going on. Thanks. I have been poking about with my Patchy VM today and thought my lilypond-git was mucked up, so I ran it again to check James PS. Moving over to KVM from VirtualBox using a .raw image alone I can shave on average about 4 minutes off of my compile times - w00t! :) which is a significant improvement when you consider it used to take 20-25 minutes for patchy to run from start to finish now I can nearly break the 15 minute barrier...need to see if I can squeeze any more out my dell with the PVirt drivers. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Center a number above a measure - Issue 2445
David, I saw that Colin had opened a tracker for your *ly file http://code.google.com/p/lilypond/issues/detail?id=2445 I'm not a code developer, however I think it might be better to also open a Rietveld issue so that it gets a proper review, from my own experience, it is more likely to be looked at there than in the google tracker - simply because it is easier to read and comment inline. I don't know if you are familiar with that process, then if you are serious about getting this into the LilyPond code, you can work on it here and post the suggested changes etc. I fear otherwise it will stagnate *just* an attachment on a tracker. You can use git-cl to ease the process of uploading and updating both Rietveld and the tracker at the same time. http://lilypond.org/doc/v2.15/Documentation/contributor/summary-for-experienced-developers It doesn't mean that it has to compile necessarily or be perfect from the 'start' (for instance Mike Solomon often throws up 'concept' patches or 'work in progress' patches/code to Rietveld for comment. Sometimes they die there but more often than not they get improved very quickly simply because of the way to compare and share information in Rietveld. regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Avoiding tie/prall collision
Helge, On 11 April 2012 13:02, Helge Kruse helge.kruse-nos...@gmx.net wrote: Am 11.04.2012 19:24, schrieb James: Well it requires that any changes I do in the English document are picked up and translated by the trasnaltors. The assumption is that those that do the German Translating see my checkins and make the same changes in the german doc. They do for the Spanish and French, but I think that is simply because the two or three that do that are always looking for it. Virtually all the checkins I do are for doc only and so the translators can easily see what I have done and if they need to make the changes in their docs too. But the translations are handled separately from the English documents, so it is very likely the different translations are not always consistent. Patches are always welcome :) often I see the German translation gets 'left behind' compared to the Spanish, French and Japanese versions. The two sentences in German would be something like this: In mehrstimmiger Musik ist es im Allgemeinen besser, die Stimme explizit mit voice auszuwählen anstatt die Ausrichtung einzelner Objekte zu ändern. Für weitere Informationen siehe: Multiple voices. But this may differ in style from the original translators. I am not in the team yet. I don't know if there is a need for additional translation support. Further I don't know how to see this checkins. Does it make sense to learn how to see this and to add annotations/additions? I could give it a try. Or did I missed just one cycle? http://lilypond.org/doc/v2.15/Documentation/contributor/translating-the-documentation.html Start here. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
Federico, On 14 April 2012 10:57, Federico Bruni fedel...@gmail.com wrote: Hi, I started using version 2.13.56 and I realized that this bug seems fixed: http://code.google.com/p/lilypond/issues/detail?id=1459 As hideNotes/unHideNotes work fine in TabStaff now, I'm thinking that it would be nice to add a TabNoteHead override/revert in their definitions in property-init.ly Two years ago Marc expressed some concern about including TabNoteHead inside hideNotes/unHideNotes, because unHideNotes reverts the transparency of objects (such as stems and dots) that shouldn't be displayed in TabStaff: http://lists.gnu.org/archive/html/lilypond-user/2010-01/msg00634.html I've made some tests and I think that there's no reason for such a concern. Everything looks fine to me (see the attached snippet). Sure, I'm missing something :) I believe that we don't need a specific command for hiding TabNoteHead. I always use Staff and TabStaff: both should display (or hide) the same music, I can't imagine a situation where I'd like to hide a note in Staff and not in TabStaff. What do you think about it? I think 'user' isn't the email list you really need to send this to but dev. Also I see have already updated the Tracker. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
Hello, On 14 April 2012 15:47, Marc Hohl m...@hohlart.de wrote: Am 14.04.2012 11:57, schrieb Federico Bruni: Hi, I started using version 2.13.56 and I realized that this bug seems fixed: http://code.google.com/p/lilypond/issues/detail?id=1459 I'll verify that if no one else has. I am building a latest version at the moment of 2.15.x However reading the tracker again just now, are the comments from this morning a 'new' issue or an 'enhancement' if so, we need a new tracker. Could Federico or Marc clarify please? James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
Hello, On 15 April 2012 07:13, Federico Bruni fedel...@gmail.com wrote: Il 14/04/2012 21:09, James ha scritto: Hello, On 14 April 2012 15:47, Marc Hohlm...@hohlart.de wrote: Am 14.04.2012 11:57, schrieb Federico Bruni: Hi, I started using version 2.13.56 and I realized that this bug seems fixed: http://code.google.com/p/lilypond/issues/detail?id=1459 I'll verify that if no one else has. I am building a latest version at the moment of 2.15.x I've tested it now on latest version of lilypond/translation branch. It works fine. Right so Issue 1459 is fixed? However reading the tracker again just now, are the comments from this morning a 'new' issue or an 'enhancement' if so, we need a new tracker. Could Federico or Marc clarify please? It's an enhancement, which has already been discussed before (see links I pasted in the tracker) but never recorded in the tracker. You don't really make it easy for the bug squad - who are generally non-technical people who have enough to do without having to pick apart/read through long threads, threads I might add that have never been reported to the bug list (or dev list - that was me). Federico, it seems you have the ability (and knowledge) to create a tracker yourself so I suggest that if issue 1459 is fixed you change the label to fixed - someone else will verify - and then create a new tracker for the enhancement - whatever it is. Else whoever comes back to the old tracker has to puzzle their way through and often this puts people off (unless you yourself are going to work and create the patch). If the change is accepted, the following snippet should be removed (I think): http://lsr.dsi.unimi.it/LSR/Snippet?id=633 Add this to the same (new?) Tracker as well. We're desperately trying to make it as easy as possible for the bug squad (and developers) to workout what a tracker is for and if/when it is fixed and more importantly how to know what they are looking at. I hope you understand. james ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Problem running makelsr.py
Hello, While trying to run makelsr.py at the top level of the tree I get this error. --snip-- james@jameslilydev2:~/lilypond-git$ ./scripts/auxiliar/makelsr.py Traceback (most recent call last): File ./scripts/auxiliar/makelsr.py, line 56, in module TAGS = os.listdir (in_dir) OSError: [Errno 2] No such file or directory: '' --snip-- Am I missing something here? I cannot see any change to this script recently, I have attached a formatted patch (which I don't think is the cause - I get the same issue when I run this on a 'clean' tree) on Issue 2247 just in case, but I don't know what the problem is. Any help would be appreciated. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem running makelsr.py
Graham, On 15 April 2012 22:24, Graham Percival gra...@percival-music.ca wrote: On Sun, Apr 15, 2012 at 10:18:41PM +0100, James wrote: james@jameslilydev2:~/lilypond-git$ ./scripts/auxiliar/makelsr.py Traceback (most recent call last): File ./scripts/auxiliar/makelsr.py, line 56, in module TAGS = os.listdir (in_dir) OSError: [Errno 2] No such file or directory: '' I cannot see any change to this script recently, Phil made a recent change to avoid explicitly giving the tags, but that change isn't happy with a local makelsr.py update. He may be able to extend this to local files, but I suspect that the easiest fix will be to revert his change and just manually alter the TAGS definition. Thanks, I thought I was going mad. I haven't done a snippet/new for a while and couldn't recall anything changing. This will hold up Pavel's checkin but there is nothing riding on it, so it can wait. james ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Read error from 'delta' in Git for staging
Hello, I've noticed an problem on my git when I tried to checkout staging and then git pull -r. --snip-- james@jameslilydev2:~/lilypond-git$ git status # On branch master nothing to commit (working directory clean) james@jameslilydev2:~/lilypond-git$ git checkout staging error: failed to read object d3eee73c6d278425bcf694c7bf221dc334bd2a5f at offset 434935 from .git/objects/pack/pack-0b0c25e2ea4c8652fd7fea0ea862c9d733110161.pack Switched to branch 'staging' Your branch is behind 'origin/staging' by 9 commits, and can be fast-forwarded. james@jameslilydev2:~/lilypond-git$ git pull -r First, rewinding head to replay your work on top of it... error: failed to read delta base object d3eee73c6d278425bcf694c7bf221dc334bd2a5f at offset 434935 from .git/objects/pack/pack-0b0c25e2ea4c8652fd7fea0ea862c9d733110161.pack Fast-forwarded staging to f1defa51a982cf769172cfcdd6b2612608ba2746. james@jameslilydev2:~/lilypond-git$ gitk james@jameslilydev2:~/lilypond-git$ lily-git.tcl james@jameslilydev2:~/lilypond-git$ git branch master * staging test-staging james@jameslilydev2:~/lilypond-git$ git pull -r Current branch staging is up to date. --snip-- As you can see if I keep doing a git pull -r the error 'goes away'. This is my patchy VM but I get no physical device (disk read errors) either on the VM or the underlying host. As Master and Staging are both on the same commit and because read errors are always worrying (especially to someone who works in the Storage Industry), Perhaps this is overkill, but there isn't anything urgent on, and I have backups of this VM - if anyone wants me to do 'stuff' on this install - I'm going to blow my complete VM away, reinstall LilyDev and download $LILYPOND_GIT from scratch. This will take an hour or so on my connection, so Patchy merge won't run until I get up tomorrow morning. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
git fetch with Lily-git.tcl
Hello, I was struggling a bit this morning getting my lilydev env to work with patchy, once I had deleted my $LILYPOND_GIT (because git was reporting read errors on a hash). After a bit of head scratching and then realising I hadn't set up the ssh part, I still was struggling to get patchy to even start. It kept complaining abuot the old 'shallow repository' :) gitk and git index only showed the last two commits in both staging and master (which happened to be identical). I kept a few mails that David sent a few months back and he suggested git fetch --depth=100 Which seemed to do the trick, gitk showed everything and patchy worked again - huzzah! Now I looked at Lily-git and found the lines where the 'update' button doubles as 'get source' and it has the following --snip-- ... git remote add -t $originHead \ origin git://git.sv.gnu.org/lilypond.git git fetch git reset --hard origin/$originHead ... --snip-- I wondered if we should inspite (or because of?) Lily-git being aimed beginner devs that adding the extra --depth command? or would that be harmful? It seems Patchy needs it (or did in my case) if you jump right in and follow the CG and then try to get patchy running. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: State of the pond
Hello, On 19 April 2012 20:52, David Kastrup d...@gnu.org wrote: Graham Percival gra...@percival-music.ca writes: SLOWER DEVELOPMENT Development has slowed to a trickle. I'm not certain if this is just because it's late spring (i.e. busy academic time), or if people are holding their breaths waiting for the stable release (i.e. not putting forward any major patches), or just everybody getting older. I am partly responsible. For one thing I've been climbing around Easter, for another I am brooding over the best way to work on user-definable new events, grobs, other things. I am coding far too little and brooding far too much: I am not really all that content with my current approaches of making LilyPond extensible in that area while not impacting performance more than inevitable. VACATION On a personal note, I'm off to Europe from May 8 to 24, seeing Zurich, Munich, Salzburg, Vienna, Prague, and Germany (in that order). It will be interesting to hear how you manage to visit Munich as second city while holding off on Germany till the end. You obviously don't work with Bavarians (like I do). :) James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Footnote documentation error
Hello, On 20 April 2012 00:40, Nick Payne nick.pa...@internode.on.net wrote: The documentation at http://lilypond.org/doc/v2.15/Documentation/notation/creating-footnotes for both automatic and manual footnotes says that the \footnote command must come *before* the grob to which the footnote is being attached. This doesn't seem to be the case. Here the \footnote commands are after the notes to which they are attached, and they work fine: I think this was to do with David's additional work on Mike's a few months ago when what he did changed the requirement from the original footnote document in earlier versions of 2.15. We did re-write much of the examples and obviously missed this. Before I create a tracker, I'll wait for a confirmation from David/Mike that this is technically correct. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Regarding LSR translation work
Hello, On 21 April 2012 10:13, Jean-Charles Malahieude lily...@orange.fr wrote: ... This makes me believe it would be a good opportunity to have the English version follow the same rule as translations. Err.. not sure what you mean by that technically but it's complicated enough with snippets as it is, to follow the translation method adds even more complexity (if the CG is anything to go by). Remember that unless you are doing this all the time (which the translators will be) it isn't that straightforward. We want to encourage contributors not push them away. From a very basic-no-progamming skill perspective, why can't we just have an extra texidoc entry in the snippet itself and add the translation manually, like we would for any updated snippet? Having another set of files to edit just to put in an explanation seems silly and now we have to link files to those as well? So in the NR we have an @snippet that links to a dir with the snippet that now has to link to a texidoc for that snippet in another dir. How is that better? In fact, why do we even need a texidoc string *inside* the snippet? I don't use one for @lilypond examples. Why not explicitly translate the snippet 'text' in the manual like we do for everything else. Wouldn't that be easier long term? James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: State of the pond
Hello, On 22 April 2012 00:02, Francisco Vila paconet@gmail.com wrote: 2012/4/20 Graham Percival gra...@percival-music.ca: We do not have a long history of flawless git actions from translations, so my preference would be not to touch anything. Good idea! The definitive recipe for eternal flawless development is not to touch anything, ever. Better safe than sorry. Gosh! Talk about taking something out of context. No one said 'ever' - you said that, consider this a moment of 'reflection', if you want an analogy. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Footnote documentation error
Hello, On 22 April 2012 04:12, Mark Mathias d8val...@gmail.com wrote: So... as far as the Bug Squad is concerned, are we still waiting for something or does this need to get added to the tracker? Thanks, Mark As far as the bug squad are concerned - being one myself - we'd like a confirmation that this is a documentation error or an unexpected/inconsistent behaviour in the code. I haven't seen a case for either yet. james ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: State of the pond
Hello, On 22 April 2012 11:59, David Kastrup d...@gnu.org wrote: Werner LEMBERG w...@gnu.org writes: Git history will judge us all. Interesting. Up to now I've assumed God does this. If HE weren't a fan of distributed version control systems, why create the world in the first place? God Loves Git Now there's a rallying cry/T-shirt slogan if ever I've heard one! James PS For all those who are not British, I don't think I can convey the absolute simple pleasure that I (at least, perhaps others) get from having a DVCS called 'Git' :) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: What's with the test-patches volunteers?
Hello, On 22 April 2012 16:00, Colin Campbell c...@shaw.ca wrote: On 12-04-22 03:57 AM, Phil Holmes wrote: - Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Sunday, April 22, 2012 7:31 AM Subject: What's with the test-patches volunteers? It is close to two months that I have been the only person running test-patches, even though several volunteers claimed they would do so. It has been the main reason I shelled out €20 for a week of internet access during my spring vacation. My home machine stays powered and idle, except for BOINC, while I'm at the office. With a bit of a leg up, I can help out by way of a cron job. This isn't 'that' patchy - you cannot really cron it Needs a bit of human input. http://lilypond.org/doc/v2.15/Documentation/contributor/patchy Specifically - test-patches.py: I already run lilypond-patchy-staging.py on my machine, you don't need to worry about that so much. Graham calls it all 'patchy' - I like to think of them as Brother and Sister. ;) Patchy and Patchita chuckle James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046)
Hello, On 26 April 2012 07:55, m...@apollinemike.com m...@apollinemike.com wrote: On 26 avr. 2012, at 07:28, Graham Percival wrote: Well, right now we have nobody running the automated tests to check that new patches are ok. So there will be no patches accepted to lilypond. I have a meeting in mid-May w/ the University of Paris VIII. They're donating a computer to LilyPond and I'll set patchy up on it. While you can set up and cron patchy-merge-staging, patchy-test-patches still needs 'human' interaction (reg tests). Perhaps this computer could be better spent doing other LP related things Donate cycles for devs for instance via SSH - David might be appreciative of that. I've run patchy-test just now for the three patches outstanding this morning. It's no a big deal, I've just never got round to running the patchy-test scripts (well since the scripts were very first created when I had trouble understanding them), so don't worry about patches David now, I'll pick up the slack here. Patchy-merge already runs on my box pretty seamlessly and I can run patchy-test over coffee most mornings now I know what is involved. I'll also look at updating the CG instructions because while it is relatively simple, a non-dev like me always has trouble, initially, getting all my ducks in a row with regard to setting up LP source code, getting patchy downloaded and configured and then running her. Regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
