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: Patch push announcements
On Tue, Apr 03, 2012 at 09:20:08PM -0600, Colin Campbell 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. It formely went to bug-lilypond. I wonder if the owners are getting the notification, and if so, how we handle those tracker items which do not have an owner? Issue owners will get a personal mail unless they un-star that issue. If they deliberately un-star an issue, then they can either check it manually, or else sign up for lilypond-auto and see all the messages. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch push announcements
On Wed, Apr 04, 2012 at 08:33:27AM +0100, James wrote: 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. Just leave those for Mike to push. We're not in any rush. I've been pushing patches (Alberto, Pavel, Peter) for those trackers that don't have a dev who has push access, yes, because we don't have a Frog meister. Or do we? I honestly can't remember what happened the last time it came up. 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. doesn't git-cl assign an owner? if not, it should. There's no reason why a human needs to do this manually. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LSR is now on 2.14
- Original Message - From: Thomas Morley thomasmorle...@googlemail.com To: Phil Holmes m...@philholmes.net Cc: David Nalesnik david.nales...@gmail.com; lilypond-devel lilypond-devel@gnu.org Sent: Tuesday, April 03, 2012 10:33 PM Subject: Re: LSR is now on 2.14 Am 3. April 2012 16:30 schrieb Phil Holmes m...@philholmes.net: My understanding is that, once a correct snippet is in the LSR, it should be deleted from snippets/new. What will then happen is that I will grab an updated tarball of the snippets tagged with the docs tag and run makelsr. These will then all be imported into snippets (not snippets/new). If there is a snippet in snippets/new it over-writes the one from the tarball. So the next task is to check whether there are any snippets in snippets/new that should not be deleted - these would be ones that only run on 2.15.x. I'm not sure how to continue: I just downloaded the source-tarball, lilypond-2.15.35.tar.gz and sorted the 2.14-snippets from *Documentation/snippets/new/ I noticed that these snippets are not completely identical to the ones from Savannah: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree;f=Documentation/snippets/new;h=cac0bba81f655a2666049823e7d21ec51bcd73cd;hb=2055f35c47a045a50a01ff4dba8524322cfc3b48 What to do? -Harm = Savannah will only catch up when I've run makelsr from the tarball and pushed the changes to git. I want a clear run at that, and so am planning to do it over the weekend. Could you confirm that all the snippets shown in Savannah/snippets/new can be removed/deleted? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
LSR on 2.14 or not?
Sorry to butt in, but I want to confirm stuff. 1) is LSR running 2.14.2 right now? 2) how many files were uncompilable? I am aware of one file, which I believe we deleted. Were there any other problematic files? 3) can we do a mundane LSR import? i.e. don't touch anything in Documentation/snippets/new/; just do an ordinary full LSR import. If there's nothing suspicious in the diff go ahead and push directly to staging, but I wouldn't mind seeing a patch on rietveld just for peace of mind. ** only after ** all the above steps are complete should we investigate Documentation/snippets/new. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LSR on 2.14 or not?
Am 4. April 2012 10:36 schrieb Graham Percival gra...@percival-music.ca: Sorry to butt in, but I want to confirm stuff. 1) is LSR running 2.14.2 right now? Yes. 2) how many files were uncompilable? I am aware of one file, which I believe we deleted. Were there any other problematic files? contemporary-vibrato.ly didn't compile and was deleted for now. filtering-parts-from-the-command-line.ly showed a lexer-bug. AFAIK, the bug was fixed by David Kastrup and David Nalesnik found an in-file work-around. All other files are compiling after running convert-ly or with additional manual work. 3) can we do a mundane LSR import? i.e. don't touch anything in Documentation/snippets/new/; just do an ordinary full LSR import. If there's nothing suspicious in the diff go ahead and push directly to staging, but I wouldn't mind seeing a patch on rietveld just for peace of mind. Can't do it myself. ** only after ** all the above steps are complete should we investigate Documentation/snippets/new. Ok -Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
benchmarking LilyPond output: would you like some analysis?
Dear Team, looks that taking a break in LilyPond work is impossible for me... ;) How did you like the colorful Credo example posted in the LilyPond Report #25 (http://news.lilynet.net/?The-LilyPond-Report-25lang=en#the_game_of_the_month)? Would you like to see a more detailed analysis of some Lily engraving, as it was done in the old times http://lilypond.org/web/about/automated-engraving/schubert? I could write something in spare time - if you are interested. cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch push announcements
Graham Percival gra...@percival-music.ca writes: On Wed, Apr 04, 2012 at 08:33:27AM +0100, James wrote: 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. Just leave those for Mike to push. We're not in any rush. I've been pushing patches (Alberto, Pavel, Peter) for those trackers that don't have a dev who has push access, yes, because we don't have a Frog meister. Or do we? I honestly can't remember what happened the last time it came up. 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. doesn't git-cl assign an owner? if not, it should. There's no reason why a human needs to do this manually. It definitely doesn't. And state Accepted instead of Started is also less than optimal for starting a review. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: benchmarking LilyPond output: would you like some analysis?
On 4 April 2012 13:06, Janek Warchoł janek.lilyp...@gmail.com wrote: How did you like the colorful Credo example posted in the LilyPond Report #25 ( http://news.lilynet.net/?The-LilyPond-Report-25lang=en#the_game_of_the_month )? *The Credo file is not colorful. It's just black and white, as usual.* * * Łukasz ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: benchmarking LilyPond output: would you like some analysis?
On 4 April 2012 15:05, Łukasz Czerwiński milimet...@gmail.com wrote: On 4 April 2012 13:06, Janek Warchoł janek.lilyp...@gmail.com wrote: How did you like the colorful Credo example posted in the LilyPond Report #25 ( http://news.lilynet.net/?The-LilyPond-Report-25lang=en#the_game_of_the_month )? *The Credo file is not colorful. It's just black and white, as usual.* * * Łukasz Under the Janek's link there was a standard bw pdf, while the colorful one was hidden two paragraphs below. I'm sorry for spamming you with my previous mail. Łukasz ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LSR on 2.14 or not?
- Original Message - From: Graham Percival gra...@percival-music.ca To: Thomas Morley thomasmorle...@googlemail.com; David Nalesnik david.nales...@gmail.com; Phil Holmes m...@philholmes.net Cc: lilypond-devel lilypond-devel@gnu.org Sent: Wednesday, April 04, 2012 9:36 AM Subject: LSR on 2.14 or not? Sorry to butt in, but I want to confirm stuff. 1) is LSR running 2.14.2 right now? 2) how many files were uncompilable? I am aware of one file, which I believe we deleted. Were there any other problematic files? 3) can we do a mundane LSR import? i.e. don't touch anything in Documentation/snippets/new/; just do an ordinary full LSR import. If there's nothing suspicious in the diff go ahead and push directly to staging, but I wouldn't mind seeing a patch on rietveld just for peace of mind. ** only after ** all the above steps are complete should we investigate Documentation/snippets/new. - Graham It's on my work stack. Today I'm going to update the LSR itself to add the docs tag to the files we added manually - these came from snippets/new. I'll also do a local makelsr run and check and push. I'm going to wait until I have time (possibly Thursday evening, but may be the weekend) and get the docs tarball and run makelsr against it. That'll go on Rietveld and I'm likely to run patchy-test against it myself. If that's OK we'll cross-check which files should be deleted from /new, delete them and patch, review and push. Then I think we can confirm that the needed work has been done. We then need to update the CG, I'll complete a script which prunes headers and versions from snippets, and we should check that we can test that all snippets compile for future upgrades. How does that sound? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: casual contributors (was: patch going unpushed)
Graham == Graham Percival gra...@percival-music.ca writes: Graham On Thu, Mar 22, 2012 at 11:40:43PM +, James wrote: Graham We don't really have a frog meister, so nobody is taking Graham responsibility for pushing Graham We should have somebody who takes care of contributors without Graham dedicated mentors. In mathematical/logical terms, we need a Graham barber who shaves everybody who does not shave themselves. I Graham shouldn't need to get involved when there's a new contributor, Graham much less a known+experienced contributor like Peter! One issue is that the `How to participate' webpage at http://lilypond.org/web/devel/participating/ doesn't point people at Rietveld -- it just tells them (slightly incorrectly: there's a typo in git format-patch) to send a patch to lilypond-devel. -- Dr Peter Chubb peter.chubb AT nicta.com.au http://www.ssrg.nicta.com.au Software Systems Research Group/NICTA ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
GSoC rendering improvements
Hi all, I'd be interested in working on either of two projects suggested for Google Summer of Code, most likely Improve beaming but perhaps instead Improve slurs and ties. Though LilyPond isn't currently my notation tool of choice, I believe I do have an exacting aesthetic sense that would be useful to these projects, and I have a solid background in C++ from school. I don't currently have further specific ideas beyond the outline given on the LilyPond website, but any insights into these projects, and how I should best form a GSoC proposal, would definitely be welcome. Thanks, Corey ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GSoC rendering improvements
On Apr 4, 2012, at 6:35 AM, Corey F wrote: Hi all, I'd be interested in working on either of two projects suggested for Google Summer of Code, most likely Improve beaming but perhaps instead Improve slurs and ties. Though LilyPond isn't currently my notation tool of choice, I believe I do have an exacting aesthetic sense that would be useful to these projects, and I have a solid background in C++ from school. I don't currently have further specific ideas beyond the outline given on the LilyPond website, but any insights into these projects, and how I should best form a GSoC proposal, would definitely be welcome. Thanks, Corey Hey Corey, You can check out Janek's proposal for ideas on how to put one together concerning Lilypond: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/janek_warchol/1#. Improving beaming is one of my areas of development and it is a royal pain. Most of the methods controlling beam endpoints are in beam-quanting.cc in the LilyPond source. I'd first formulate the problem in aesthetic terms (i.e. The literature shows that beams usually do X, whereas LilyPond currently does Y) and then read beam-quanting.cc to see why lilypond does Y and what types of modifications would be necessary to arrive at X. Cheers, MS___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LSR is now on 2.14
- 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. I'm assuming the others (i.e. changed versions of existing snippets) will have been imported via the tarball-Seba route. -- Phil Holmes ___ 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: LSR is now on 2.14
- Original Message - From: James pkx1...@gmail.com To: Phil Holmes m...@philholmes.net Cc: Thomas Morley thomasmorle...@googlemail.com; Graham Percival gra...@percival-music.ca; lilypond-devel lilypond-devel@gnu.org Sent: Wednesday, April 04, 2012 4:16 PM Subject: 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 No - that'll only tell me I've not done anything really stupid with makelsr. I ran it without naming a tarball, so it just updates the snippets with (I believe) anything in snippets/new. It's a sensible preparation for doing a more extensive update of the snippets from the tarball from the LSR. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Git help, please
I have read the documentation, and the CG, but still am not sufficiently sure of the answer to my following questions to go ahead. Background: it seems to me the safest way to be sure that all the updates I'm going to do to the snippets don't kill the documentation build is to test it on a clean build (which my patchy user pretty much is). I believe the easiest way to do that will be to create a patch with my normal user, upload that to a new remote branch: dev/philh; then log in to patchy, pull master, pull dev/philh and do a full make, make test, make doc. Problem is, I can't find documentation I can unerringly follow to: a) create the remote branch origin/dev/name b) push my master (or other) branch to that remote branch c) pull the changes in that branch to a local machine d) revert the patch if need be (I'd like idiot's instructions to this anyway, if possible) Can anyone help with this, please? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LSR is now on 2.14
On Wed, Apr 04, 2012 at 04:29:40PM +0100, Phil Holmes wrote: No - that'll only tell me I've not done anything really stupid with makelsr. I ran it without naming a tarball, so it just updates the snippets with (I believe) anything in snippets/new. That is correct. It also updates any translations of snippets. It's a sensible preparation for doing a more extensive update of the snippets from the tarball from the LSR. Yes, sounds good. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Git help, please
On Wed, Apr 04, 2012 at 04:37:53PM +0100, Phil Holmes wrote: Background: it seems to me the safest way to be sure that all the updates I'm going to do to the snippets don't kill the documentation build is to test it on a clean build (which my patchy user pretty much is). I believe the easiest way to do that will be to create a patch with my normal user, upload that to a new remote branch: dev/philh; then log in to patchy, pull master, pull dev/philh and do a full make, make test, make doc. ... I'm not totally certain I follow that, but I believe you are incorrect. Here's what to do: 1) make a new branch (locally). See CG git for the impatient for this. 2) run makelsr.py and point to the downloaded snippets. 3) do the security check, then commit the results. Testing comes later; you can always remove the commit if it's bad. 4) nuke your build dir. You've got a fast computer. 5) do a full doc build from scratch. That'll take, what, 8 minutes for you? :) 6) if it doesn't blow up, then either push directly to staging, or upload to rietveld. Don't worry about doing extra checks with patchy. If it passes a doc build from scratch on your computer, then it's highly unlikely to cause a problem at the patchy stage. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: casual contributors (was: patch going unpushed)
On Wed, Apr 4, 2012 at 1:31 AM, Peter Chubb l...@chubb.wattle.id.au wrote: One issue is that the `How to participate' webpage at http://lilypond.org/web/devel/participating/ doesn't point people at Rietveld -- it just tells them (slightly incorrectly: there's a typo in git format-patch) to send a patch to lilypond-devel. Oh no. n... You were hit by the Curse of The Old Website. We are sorry that we haven't found a counter-spell yet... http://lilypond.org/web is an old version of our website, not updated since 2 or 3 years. The current website is http://lilypond.org/index.html - please use this. :( I would at least try to fix this myself - but i really cannot do anything else than GSoC now :( Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Git help, please
- Original Message - From: Graham Percival gra...@percival-music.ca To: Phil Holmes em...@philholmes.net Cc: Devel lilypond-devel@gnu.org Sent: Wednesday, April 04, 2012 4:43 PM Subject: Re: Git help, please On Wed, Apr 04, 2012 at 04:37:53PM +0100, Phil Holmes wrote: Background: it seems to me the safest way to be sure that all the updates I'm going to do to the snippets don't kill the documentation build is to test it on a clean build (which my patchy user pretty much is). I believe the easiest way to do that will be to create a patch with my normal user, upload that to a new remote branch: dev/philh; then log in to patchy, pull master, pull dev/philh and do a full make, make test, make doc. ... I'm not totally certain I follow that, but I believe you are incorrect. Here's what to do: 1) make a new branch (locally). See CG git for the impatient for this. I can do this :-) 2) run makelsr.py and point to the downloaded snippets. 3) do the security check, then commit the results. Testing comes later; you can always remove the commit if it's bad. 4) nuke your build dir. You've got a fast computer. 5) do a full doc build from scratch. That'll take, what, 8 minutes for you? :) About 14, including nuke, make and make doc. 6) if it doesn't blow up, then either push directly to staging, or upload to rietveld. Don't worry about doing extra checks with patchy. If it passes a doc build from scratch on your computer, then it's highly unlikely to cause a problem at the patchy stage. I have had a problem with this in the past, which is why I was suggesting this route. I had an uncommitted file on my local machine that wasn't in master. I'd not added it with commit -a or whatever, and so my build was OK but patchy-staging fell over. I wanted to avoid the possibility. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Git help, please
On Wed, Apr 04, 2012 at 04:53:23PM +0100, Phil Holmes wrote: Don't worry about doing extra checks with patchy. If it passes a doc build from scratch on your computer, then it's highly unlikely to cause a problem at the patchy stage. I have had a problem with this in the past, which is why I was suggesting this route. I had an uncommitted file on my local machine that wasn't in master. I'd not added it with commit -a or whatever, and so my build was OK but patchy-staging fell over. I wanted to avoid the possibility. whoops, I forgot about that. Just run git status and if it doesn't complain about untracked files, you're fine. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Git help, please
- Original Message - From: Graham Percival gra...@percival-music.ca To: Phil Holmes em...@philholmes.net Cc: Devel lilypond-devel@gnu.org Sent: Wednesday, April 04, 2012 5:18 PM Subject: Re: Git help, please On Wed, Apr 04, 2012 at 04:53:23PM +0100, Phil Holmes wrote: Don't worry about doing extra checks with patchy. If it passes a doc build from scratch on your computer, then it's highly unlikely to cause a problem at the patchy stage. I have had a problem with this in the past, which is why I was suggesting this route. I had an uncommitted file on my local machine that wasn't in master. I'd not added it with commit -a or whatever, and so my build was OK but patchy-staging fell over. I wanted to avoid the possibility. whoops, I forgot about that. Just run git status and if it doesn't complain about untracked files, you're fine. - Graham It always complains about untracked files. aborted_edits and git-cl as a minimum. Until I moved all the LSR tarballs I'd put at the top of the source tree it complained about all those, too. I've now worked out how to create a remote branch. My next experiment will be to push to it. Fingers crossed. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Git help, please
Phil Holmes em...@philholmes.net writes: I have had a problem with this in the past, which is why I was suggesting this route. I had an uncommitted file on my local machine that wasn't in master. I'd not added it with commit -a or whatever, and so my build was OK but patchy-staging fell over. I wanted to avoid the possibility. git clone /my/repository /tmp/checkingplace cd /tmp/checkingplace test test test cd ~ rm -rf /tmp/checkingplace -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: benchmarking LilyPond output: would you like some analysis?
Le 04/04/2012 13:06, Janek Warchoł disait : Dear Team, looks that taking a break in LilyPond work is impossible for me... ;) How did you like the colorful Credo example posted in the LilyPond Report #25 (http://news.lilynet.net/?The-LilyPond-Report-25lang=en#the_game_of_the_month)? Not bad at all. Just a remark: is the first note of the bass part, bar 11 really a textedit://E:/dane/warsztat%20nutowy/Mozart%20-%20Credo.ly:608:2:2 ? I don't have it in my scale! You could have switch point-n-click off. Cheers, Jean-Charles ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Git help, please
- Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Wednesday, April 04, 2012 5:41 PM Subject: Re: Git help, please Phil Holmes em...@philholmes.net writes: I have had a problem with this in the past, which is why I was suggesting this route. I had an uncommitted file on my local machine that wasn't in master. I'd not added it with commit -a or whatever, and so my build was OK but patchy-staging fell over. I wanted to avoid the possibility. git clone /my/repository /tmp/checkingplace cd /tmp/checkingplace test test test cd ~ rm -rf /tmp/checkingplace Whilst I always appreciate yours and Graham's help, this has been an absolute masterclass in answering a question I didn't ask. I wasn't looking to create an alternative clone, since I already have one in my alternative user which I had been using for patchy. I feel I do need to understand git better (as you know) and I thought that using a remote branch to test my LSR update would be a great example of this. I also need to learn how to revert, and ditto applies. As a BTW - does cloning as above fetch the whole repo, or just recreate it locally? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: benchmarking LilyPond output: would you like some analysis?
On Wed, Apr 04, 2012 at 06:48:00PM +0200, Jean-Charles Malahieude wrote: Le 04/04/2012 13:06, Janek Warchoł disait : How did you like the colorful Credo example posted in the LilyPond Report #25 (http://news.lilynet.net/?The-LilyPond-Report-25lang=en#the_game_of_the_month)? Just a remark: is the first note of the bass part, bar 11 really a textedit://E:/dane/warsztat%20nutowy/Mozart%20-%20Credo.ly:608:2:2 ? woah, Janek uses windows?! (and _that's_ why we warn that textedit can be a security risk in our manual) - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: casual contributors (was: patch going unpushed)
On Wed, Apr 04, 2012 at 05:49:24PM +0200, Janek Warchoł wrote: On Wed, Apr 4, 2012 at 1:31 AM, Peter Chubb l...@chubb.wattle.id.au wrote: One issue is that the `How to participate' webpage at http://lilypond.org/web/devel/participating/ doesn't point people at Rietveld -- it just tells them (slightly incorrectly: there's a typo in git format-patch) to send a patch to lilypond-devel. True. There's also at least two places in the CG where it tells people to send patches to lilypond-devel. Oh no. n... You were hit by the Curse of The Old Website. We are sorry that we haven't found a counter-spell yet... Don't be silly, we know exactly how to fix it. In fact, I think that Julien has finished doing all the pre-requisite steps. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Git help, please
Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Wednesday, April 04, 2012 5:41 PM Subject: Re: Git help, please Phil Holmes em...@philholmes.net writes: I have had a problem with this in the past, which is why I was suggesting this route. I had an uncommitted file on my local machine that wasn't in master. I'd not added it with commit -a or whatever, and so my build was OK but patchy-staging fell over. I wanted to avoid the possibility. git clone /my/repository /tmp/checkingplace cd /tmp/checkingplace test test test cd ~ rm -rf /tmp/checkingplace Whilst I always appreciate yours and Graham's help, this has been an absolute masterclass in answering a question I didn't ask. I wasn't looking to create an alternative clone, since I already have one in my alternative user which I had been using for patchy. A fresh clone will not ever contain an uncommitted file. So I don't think that this advice has been as nonsensically as you assume. As a BTW - does cloning as above fetch the whole repo, or just recreate it locally? The repo is your local repository, and the current branch of _that_ is cloned and checked out. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: benchmarking LilyPond output: would you like some analysis?
On Wed, Apr 4, 2012 at 3:25 PM, Łukasz Czerwiński milimet...@gmail.com wrote: On 4 April 2012 15:05, Łukasz Czerwiński milimet...@gmail.com wrote: On 4 April 2012 13:06, Janek Warchoł janek.lilyp...@gmail.com wrote: How did you like the colorful Credo example posted in the LilyPond Report #25 (http://news.lilynet.net/?The-LilyPond-Report-25lang=en#the_game_of_the_month)? The Credo file is not colorful. It's just black and white, as usual. Under the Janek's link there was a standard bw pdf, while the colorful one was hidden two paragraphs below. Yup. The colorful solution didn't have it's own section, so i couldn't link directly to it. Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: benchmarking LilyPond output: would you like some analysis?
On Wed, Apr 4, 2012 at 6:52 PM, Graham Percival gra...@percival-music.ca wrote: On Wed, Apr 04, 2012 at 06:48:00PM +0200, Jean-Charles Malahieude wrote: Le 04/04/2012 13:06, Janek Warchoł disait : How did you like the colorful Credo example posted in the LilyPond Report #25 (http://news.lilynet.net/?The-LilyPond-Report-25lang=en#the_game_of_the_month)? Just a remark: is the first note of the bass part, bar 11 really a textedit://E:/dane/warsztat%20nutowy/Mozart%20-%20Credo.ly:608:2:2 ? woah, Janek uses windows?! Why is that surprising? I don't often wear a tuxedo, nor resemble a penguin in any other way :D Or did you think that i use Mac? (and _that's_ why we warn that textedit can be a security risk in our manual) i forgot about point-and-click all the time. I'm wondering whether we could turn it off by default - it's useful with tools like Frescobaldi, which should be smart enough to know how to invoke Lily with appropriate option on its own. cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: benchmarking LilyPond output: would you like some analysis?
On Wed, Apr 4, 2012 at 9:44 PM, Janek Warchoł janek.lilyp...@gmail.com wrote: On Wed, Apr 4, 2012 at 3:25 PM, Łukasz Czerwiński milimet...@gmail.com wrote: On 4 April 2012 15:05, Łukasz Czerwiński milimet...@gmail.com wrote: On 4 April 2012 13:06, Janek Warchoł janek.lilyp...@gmail.com wrote: How did you like the colorful Credo example posted in the LilyPond Report #25 (http://news.lilynet.net/?The-LilyPond-Report-25lang=en#the_game_of_the_month)? The Credo file is not colorful. It's just black and white, as usual. Under the Janek's link there was a standard bw pdf, while the colorful one was hidden two paragraphs below. Yup. The colorful solution didn't have it's own section, so i couldn't link directly to it. No wait, i'm wrong. I could've used direct link to pdf, sorry. http://news.lilynet.net/IMG/pdf/Coronation_Mass_-_Credo_2-15-33_marked.pdf J ___ 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)
James == James pkx1...@gmail.com writes: James 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. James Thanks, pushed as James author Peter Chubb peter.ch...@nicta.com.au Wed, 14 Mar 2012 James 22:48:52 + (09:48 +1100) committer James Lowe James pkx1...@gmail.com Wed, 4 Apr 2012 08:12:52 + (09:12 James +0100) commit 42ca3ff037c8ca7a7c65bf3b1423dfcb5d974d2e James Can you close your Rietveld issue? Looks like someone else already has closed it. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GSoC rendering improvements
Hi Corey,
On Apr 4, 2012, at 6:35 AM, Corey F wrote:
I'd be interested in working on either of two projects suggested for Google
Summer of Code, most likely Improve beaming but perhaps instead Improve
slurs and ties.
Glad to hear that you're interested in those!
Though LilyPond isn't currently my notation tool of choice, I believe I do
have an exacting aesthetic sense that would be useful to these projects,
I suggest you to go here
http://news.lilynet.net/IMG/pdf/Coronation_Mass_-_Credo_2-15-33_marked.pdf
and check whether yellow, orange and brown markings surprise you or
not. That could be a good test.
I don't currently have further specific ideas beyond the outline given on
the LilyPond website, but any insights into these projects, and how I should
best form a GSoC proposal, would definitely be welcome.
On Wed, Apr 4, 2012 at 3:47 PM, m...@apollinemike.com
m...@apollinemike.com wrote:
I'd first formulate the problem in aesthetic terms
(i.e. The literature shows that beams usually do X, whereas LilyPond
currently does Y) and then read beam-quanting.cc to see why lilypond does Y
and what types of modifications would be necessary to arrive at X.
I think there might not be enough time to define all specific changes
that are needed in beam positions or tie and slur shapes before
application deadline - it's a lot of work. However, you can try
describing some general changes, for example:
- change beam thickness and beam gap according to staff size
(something similar to optical sizing
http://lilypond.org/doc/v2.15/Documentation/essay/engraving-details#optical-sizing),
- when beam gap is small, hide stafflines that show in these gaps to
increase legibility
- make beaming depend on context (surrounding notes)
- automatically adjust beam gap and line thickness to allow better beam quanting
- make beaming more consistent (a bad output example: { e''8[ c'']
d''[ b'] c''[ a'] } )
- make beam collision avoidance more precise (currently it sometimes
moves the beams too much)
- make beam position quanting less strict
If you want, i can send you my (huge) collection of examples about
beams and ties.
cheers,
Janek
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GSoC rendering improvements
On 04/04/2012 01:27 PM, Janek Warchoł wrote: I suggest you to go here http://news.lilynet.net/IMG/pdf/Coronation_Mass_-_Credo_2-15-33_marked.pdf and check whether yellow, orange and brown markings surprise you or not. That could be a good test. Thanks. I do recognize for most of those marked elements that something's a little off -- moreso with the slurs/ties so perhaps I will look into focusing on those. I don't currently have further specific ideas beyond the outline given on the LilyPond website, but any insights into these projects, and how I should best form a GSoC proposal, would definitely be welcome. On Wed, Apr 4, 2012 at 3:47 PM, m...@apollinemike.com m...@apollinemike.com wrote: I'd first formulate the problem in aesthetic terms (i.e. The literature shows that beams usually do X, whereas LilyPond currently does Y) and then read beam-quanting.cc to see why lilypond does Y and what types of modifications would be necessary to arrive at X. I think there might not be enough time to define all specific changes that are needed in beam positions or tie and slur shapes before application deadline - it's a lot of work. However, you can try describing some general changes, for example: Yes, although I'll try to outline some significant changes, I think most of the work collecting specific problems and examples from the literature will have to take place in the early stages of the project. I'll give some thought to how to approach that process. Thank you both for your help and insights -- I'll hope to put together an application (while still keeping up with school etc. this week...) Corey ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
