Re: musicxml2ly
On Sun, 8 Apr 2012, Martin Tarenskeen wrote: The good news is that in many cases only a little editing of the .ly file is required to turn a bad conversion into a good one. For example, all lead sheets from Wikifonia that I have tried have the Chords printed below instead of above the staff. I remember this had been fixed in one of the previous lilypond 2.15.x versions, but with musicxml2ly from Lilypond 2.15.37 I am still (again?) having this problem. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: commit access
Benkő Pál benko@gmail.com writes: dear team and Project Manager, I'd like to get commit access. I have checked in several of Pál's commits in the past. Just recently another commit that had passed review. For better or worse, I have not personally proofread the commit before checking it in (so it is missing a SignedOffBy from me). So with regard to coder responsibility, giving Pál commit access would not make much of a difference anymore. It would enable him to bypass procedures. I'd strongly suggest that he read through the current version of the contributors' guide in order to make sure that there are no significant surprises for him lurking in there. And remind him that patches he commits under his name have the copyright attributed to him and nobody else, so he should be careful about using external sources, even freely licensed ones. I support his request. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Doc build hanging (with memory leak?)
Hello all, I've successfully build Lilypond itself from source, but when I try to make doc, the build hangs on the first file it attempts to compile: make[3]: Entering directory `/home/joseph/code/lily/build/input/regression' LILYPOND_VERSION=2.15.39 /usr/bin/python /home/joseph/code/lily/scripts/lilypond-book.py -I /home/joseph/code/lily/input/regression/ -I ./out-www -I /home/joseph/code/lily/input -I /home/joseph/code/lily/Documentation -I /home/joseph/code/lily/Documentation/snippets -I /home/joseph/code/lily/input/regression/ -I /home/joseph/code/lily/Documentation/included/ -I /home/joseph/code/lily/build/mf/out/ -I /home/joseph/code/lily/build/mf/out/ -I /home/joseph/code/lily/Documentation/pictures -I /home/joseph/code/lily/build/Documentation/pictures/./out-www --process='/home/joseph/code/lily/build/out/bin/lilypond -I /home/joseph/code/lily/input/regression/ -I ./out-www -I /home/joseph/code/lily/input -I /home/joseph/code/lily/Documentation -I /home/joseph/code/lily/Documentation/snippets -I /home/joseph/code/lily/input/regression/ -I /home/joseph/code/lily/Documentation/included/ -I /home/joseph/code/lily/build/mf/out/ -I /home/joseph/code/lily/build/mf/out/ -I /home/joseph/code/lily/Documentation/pictures -I /home/joseph/code/lily/build/Documentation/pictures/./out-www -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out-www --format=texi-html --loglevel=WARN --lily-output-dir /home/joseph/code/lily/build/out/lybook-db --redirect-lilypond-output out-www/collated-files.tely langdefs.py: warning: lilypond-doc gettext domain not found. Checking 'top' shows that the memory consumption of Lilypond is steadily increasing over time, but nothing appears to actually be happening. This is completely at odds with the last doc builds I attempted for Lilypond, probably late last year. Is this a bug, or is the doc build system just operating differently? Thanks and best wishes, -- Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc build hanging (with memory leak?)
- Original Message - From: Joseph Rushton Wakeling joseph.wakel...@webdrake.net To: lilypond-devel@gnu.org Sent: Saturday, May 12, 2012 8:37 AM Subject: Doc build hanging (with memory leak?) Hello all, I've successfully build Lilypond itself from source, but when I try to make doc, the build hangs on the first file it attempts to compile: make[3]: Entering directory `/home/joseph/code/lily/build/input/regression' LILYPOND_VERSION=2.15.39 /usr/bin/python /home/joseph/code/lily/scripts/lilypond-book.py -I /home/joseph/code/lily/input/regression/ -I ./out-www -I /home/joseph/code/lily/input -I /home/joseph/code/lily/Documentation -I /home/joseph/code/lily/Documentation/snippets -I /home/joseph/code/lily/input/regression/ -I /home/joseph/code/lily/Documentation/included/ -I /home/joseph/code/lily/build/mf/out/ -I /home/joseph/code/lily/build/mf/out/ -I /home/joseph/code/lily/Documentation/pictures -I /home/joseph/code/lily/build/Documentation/pictures/./out-www --process='/home/joseph/code/lily/build/out/bin/lilypond -I /home/joseph/code/lily/input/regression/ -I ./out-www -I /home/joseph/code/lily/input -I /home/joseph/code/lily/Documentation -I /home/joseph/code/lily/Documentation/snippets -I /home/joseph/code/lily/input/regression/ -I /home/joseph/code/lily/Documentation/included/ -I /home/joseph/code/lily/build/mf/out/ -I /home/joseph/code/lily/build/mf/out/ -I /home/joseph/code/lily/Documentation/pictures -I /home/joseph/code/lily/build/Documentation/pictures/./out-www -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out-www --format=texi-html --loglevel=WARN --lily-output-dir /home/joseph/code/lily/build/out/lybook-db --redirect-lilypond-output out-www/collated-files.tely langdefs.py: warning: lilypond-doc gettext domain not found. Checking 'top' shows that the memory consumption of Lilypond is steadily increasing over time, but nothing appears to actually be happening. This is completely at odds with the last doc builds I attempted for Lilypond, probably late last year. Is this a bug, or is the doc build system just operating differently? Thanks and best wishes, The doc build now issues far less chatter than it used to. With a single core machine, it could well go an hour without a single message. If it's using CPU and taking memory, be patient. If there's no response after a day, let us know. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Fwd: LoMus 2012
Begin forwarded message: From: Thierry Coduys thierry.cod...@le-hub.org Subject: LoMus 2012 Date: 12 mai 2012 12:15:03 HAEC To: m...@mikesolomon.org Dear Mike, The jury wishes to congratulate you on your LilyPond open source software, that won the First Prize at the LoMus 2012 contest. A cheque or bank transfer of 2000 € will be sent to you by the AFIM. Could you kindly let us know if the following is the right postal address ? 1, rue Hurtziger 92110 Clichy France Please accept our warmest regards and don't hesitate to contact me for any further information. Thierry Coduys w00t! Mazal tov to everyone! ~Mike___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: LoMus 2012
m...@mikesolomon.org m...@mikesolomon.org writes: Begin forwarded message: From: Thierry Coduys thierry.cod...@le-hub.org Subject: LoMus 2012 Date: 12 mai 2012 12:15:03 HAEC To: m...@mikesolomon.org Dear Mike, The jury wishes to congratulate you on your LilyPond open source software, that won the First Prize at the LoMus 2012 contest. A cheque or bank transfer of 2000 € will be sent to you by the AFIM. Could you kindly let us know if the following is the right postal address ? 1, rue Hurtziger 92110 Clichy France Please accept our warmest regards and don't hesitate to contact me for any further information. w00t! Mazal tov to everyone! Graham's worst fears... If I remember correctly, we had two applications for the Google Summer of Code, and only one has been accepted under the GNU umbrella. Before dispersion fights start, it might make sense asking the other applicant whether an admittedly smaller sum like this might enable him to embark on his project or part of it. It would appear that the prize itself would be newsworthy for trying to convince schools particularly in France to consider opening venues for their coursework to make use of LilyPond, an enterprise that Valentin has previously undertaken with somewhat lukewarm results IIRC. Make a ponding of the award, and point to the contest site (if any) for the details. Like the awarded sum. I'd find it weird to flash numbers on our main website. Certainly a nice endorsal. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
Hi Mike, Congratulations! (To everyone!!) Best regards, Kieren. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
On 12 mai 2012, at 12:37, David Kastrup wrote: m...@mikesolomon.org m...@mikesolomon.org writes: Begin forwarded message: From: Thierry Coduys thierry.cod...@le-hub.org Subject: LoMus 2012 Date: 12 mai 2012 12:15:03 HAEC To: m...@mikesolomon.org Dear Mike, The jury wishes to congratulate you on your LilyPond open source software, that won the First Prize at the LoMus 2012 contest. A cheque or bank transfer of 2000 € will be sent to you by the AFIM. Could you kindly let us know if the following is the right postal address ? 1, rue Hurtziger 92110 Clichy France Please accept our warmest regards and don't hesitate to contact me for any further information. w00t! Mazal tov to everyone! Graham's worst fears... If I remember correctly, we had two applications for the Google Summer of Code, and only one has been accepted under the GNU umbrella. Before dispersion fights start, it might make sense asking the other applicant whether an admittedly smaller sum like this might enable him to embark on his project or part of it. I wouldn't mind using it to finish my skyline work! That'll easily be five weeks of my life (around 1 000 €), and it'd allow me to focus on something other than fundraising... I'd rather keep the award for people on the development team, as it has been officially given to the people on the author's list on the website (that's who I put on the application). There'll be no dispersion fight. No worst fears. It'll be very simple. As agreed upon before I applied: 1) Within one (1) week from the timestamp on this e-mail, send me an e-mail letting me know if you have any projects that this could be used for. No need to write anything elaborate: I know you, I know LilyPond, and I know how hard it is to fix things. 2-3 sentences will suffice! 2) Give me an amount, in euros, that you need for this project. I'll dole it out accordingly and send an e-mail to the list letting them know what I did. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
m...@apollinemike.com m...@apollinemike.com writes: I wouldn't mind using it to finish my skyline work! That'll easily be five weeks of my life (around 1 000 €), and it'd allow me to focus on something other than fundraising... Well, the agreement was whoever submits and collects, decides how to distribute, and I doubt anybody would be adverse to good skylines. Figure in another five weeks for dealing with requests for code documentation and another five for dealing with regressions, and you are not exactly going to end up ahead, anyway. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
On 12 mai 2012, at 13:00, David Kastrup wrote: m...@apollinemike.com m...@apollinemike.com writes: I wouldn't mind using it to finish my skyline work! That'll easily be five weeks of my life (around 1 000 €), and it'd allow me to focus on something other than fundraising... Well, the agreement was whoever submits and collects, decides how to distribute, and I doubt anybody would be adverse to good skylines. Figure in another five weeks for dealing with requests for code documentation and another five for dealing with regressions, and you are not exactly going to end up ahead, anyway. This is not untrue... :) Bottom line - CONGRATS TO EVERYONE. This is the most prestigious open-source music software competition in the world. Get excited! ~Mike ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
m...@apollinemike.com m...@apollinemike.com writes: On 12 mai 2012, at 13:00, David Kastrup wrote: m...@apollinemike.com m...@apollinemike.com writes: I wouldn't mind using it to finish my skyline work! That'll easily be five weeks of my life (around 1 000 €), and it'd allow me to focus on something other than fundraising... Well, the agreement was whoever submits and collects, decides how to distribute, and I doubt anybody would be adverse to good skylines. Figure in another five weeks for dealing with requests for code documentation and another five for dealing with regressions, and you are not exactly going to end up ahead, anyway. This is not untrue... :) Bottom line - CONGRATS TO EVERYONE. This is the most prestigious open-source music software competition in the world. Get excited! Well, I was going to send news of it around, but as of now, there is nothing to be seen yet: URL:http://concours.afim-asso.org/home.php. Hope they get their act together eventually, since this is definitely nice promotion material. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc build hanging (with memory leak?)
On 12/05/12 11:59, Phil Holmes wrote: The doc build now issues far less chatter than it used to. With a single core machine, it could well go an hour without a single message. If it's using CPU and taking memory, be patient. If there's no response after a day, let us know. OK, cool. It's nice that the volume of make chatter has been reduced, but quite scary to have it reduced quite so much! The build on my system starts emitting further messages after about 10-12 minutes, fairly quickly once that first build command has passed. But it falls over later: -- make[4]: Entering directory `/home/joseph/code/lily/build/input/regression/lilypond-book' /home/joseph/code/lily/./input/regression/lilypond-book/GNUmakefile:33: warning: overriding commands for target `out-www/collated-files.list' /home/joseph/code/lily/./make/lysdoc-rules.make:6: warning: ignoring old commands for target `out-www/collated-files.list' make[4]: Circular out-www/collated-files.list - suffix-tely.tely dependency dropped. make[4]: Circular out-www/collated-files.list - texinfo-include-file.tely dependency dropped. make[4]: Circular out-www/collated-files.list - texinfo-include-language-detection.tely dependency dropped. make[4]: Circular out-www/collated-files.list - texinfo-language-detection.tely dependency dropped. make[4]: Circular out-www/collated-files.list - texinfo-musicxml-file-options.tely dependency dropped. make[4]: Circular out-www/collated-files.list - texinfo-musicxml-file.tely dependency dropped. make[4]: Circular out-www/collated-files.list - texinfo-papersize-docs.tely dependency dropped. make[4]: Circular out-www/texinfo-include-file.texi - texinfo-include-file.tely dependency dropped. make[4]: Circular out-www/texinfo-include-language-detection.texi - texinfo-include-language-detection.tely dependency dropped. make[4]: Circular out-www/texinfo-language-detection.texi - texinfo-language-detection.tely dependency dropped. make[4]: Circular out-www/texinfo-musicxml-file-options.texi - texinfo-musicxml-file-options.tely dependency dropped. make[4]: Circular out-www/texinfo-musicxml-file.texi - texinfo-musicxml-file.tely dependency dropped. make[4]: Circular out-www/texinfo-papersize-docs.texi - texinfo-papersize-docs.tely dependency dropped. /home/joseph/code/lily/build/scripts/build/out/run-and-check DEPTH=../../.. AJAX_SEARCH= TOP_SRC_DIR=/home/joseph/code/lily PERL_UNICODE=SD - echo texi2html not found --error-limit=0 --I=/home/joseph/code/lily/input/regression/lilypond-book --I=./out-www -I /home/joseph/code/lily/Documentation --I=/home/joseph/code/lily/build/./out-www/xref-maps --init-file=/home/joseph/code/lily/Documentation/lilypond-texi2html.init --output=out-www/suffix-tely.html out-www/suffix-tely.texi suffix-tely.texilog.log Please check the logfile suffix-tely.texilog.log for errors make[4]: *** [out-www/suffix-tely.html] Error 127 make[4]: Leaving directory `/home/joseph/code/lily/build/input/regression/lilypond-book' make[3]: *** [WWW-1] Error 2 make[3]: Leaving directory `/home/joseph/code/lily/build/input/regression' make[2]: *** [WWW-1] Error 2 make[2]: Leaving directory `/home/joseph/code/lily/build/input' make[1]: *** [WWW-1] Error 2 make[1]: Leaving directory `/home/joseph/code/lily/build' make: *** [doc-stage-1] Error 2 -- The logfile reads: build/scripts/build/out/run-and-check: 1: eval: -: not found What's going wrong here? This is just a doc-stage-1 build attempt. I tried rerunning it with single-core make just to make sure it wasn't falling over from this, but no joy, same result. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc build hanging (with memory leak?)
Joseph Rushton Wakeling joseph.wakel...@webdrake.net writes: /home/joseph/code/lily/build/scripts/build/out/run-and-check DEPTH=../../.. AJAX_SEARCH= TOP_SRC_DIR=/home/joseph/code/lily PERL_UNICODE=SD - echo texi2html not found --error-limit=0 [...] The logfile reads: build/scripts/build/out/run-and-check: 1: eval: -: not found What's going wrong here? You are running a command - echo texi2html not found and that does not quite work. It would appear that the error handling for a missing texi2html script is totally awful. I'd install texi2html and rerun configure. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc build hanging (with memory leak?)
On 12/05/12 13:37, David Kastrup wrote: You are running a command - echo texi2html not found and that does not quite work. It would appear that the error handling for a missing texi2html script is totally awful. I'd install texi2html and rerun configure. Texi2html was already installed, but re-running configure revealed that dblatex was missing (for some reason aptitude build-dep lilypond didn't include that). Seems to be working now (can't be certain, it's still building:-). ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Plan for discussions
On Fri, May 11, 2012 at 7:44 PM, Graham Percival gra...@percival-music.ca wrote: However, I am opposed to any official (GOP or GLISS) proposals being decided at such a venue. Decided, absolutely not. Discussed, definitely. Similarly, we could have informal discussions about GOP or GLISS issues, to find out what the main concerns and options are. However, the result of that discussion would merely be a better introduction to the debate [...] Not at all, in my opinion. I think it's about the big picture stuff and general design. At the moment, i don't see any vision that we - The LilyPond Development Team - have about how the future of the project should look like, what changes in the LilyPond design should we make to make LilyPond a more efficient and easy to use tool. Having 681 open issues in the tracker doesn't mean virtually anything in this regard, at least in my opinion. These issues are mostly about specific bugs and/or specific feature requests - but how everything should work together? When i typeset music with Lily, i see some difficulties and/or defficiencies all the time. I don't even try to add feature requests to the tracker, because it would result in a complete disorganized mess. I also know that i don't have enough experience to design optimal and sound solutions for all the problems that i'm aware of - e.g. syntax for special hairpins (the ones that have to be entered with spacer rests now): i have an idea (it's a big idea, it would affect general Lily syntax), but i don't know if it's a good idea and whether it would work well with other Lily stuff and my other ideas. I could start an e-mail thread (or perhaps a dozen of threads about different related problems) about this, but it would get extremely complicated. On the other hand, face-to-face communication is way faster: I suppose that if i talked for two days with several senior developers, we could design a roadmap for Lily development that would introduce new concepts in the right order and coherent manner. So, a conference like this would enable us to ask good questions in the first place :) When we have a good set of questions with reasonable solution proposals, mailing list discussion and decisions would be more dramatically more efficient. I agree that email discussions can lead to additional misunderstandings, long latency, and can be frustrating, but they are the fairest way to conduct such business with our international team. Even a simple IRC or skype chat is difficult to coordinate; it is virtually impossible schedule one for a dozen people, and we have more than a dozen people who will be interested in GOP and GLISS questions. i know. On Fri, May 11, 2012 at 8:17 PM, Graham Percival gra...@percival-music.ca wrote: On Fri, May 11, 2012 at 01:57:08AM +0200, Janek Warchoł wrote: i suggest to discuss some communication guidelines, for example don't say It's settled then until there's more than 1 day of discussion and not all concerns have been addressed, even if you think that the decision is obvious. I think last year's GOP communications guidelines were sufficient. Hmm? I recall only one decison: Potentially sensitive or private matters will be referred to Graham. (GOP 6) It's only partially applicable to the problems we sometimes have in our discussions (in my opinion). How exactly do you suggest to change them, and why? I don't want to change GOP 6 decision. I'm wondering whether there are other communication guidelines we could have - to avoid troubles in our communication. What were the problems with GOP? there were no problems. It just didn't tackle this. Can we discuss bigger changes in syntax, too? I mean, not just the naming of commands (of course that's needed), but also the stuff that is related to how things work inside Lily. For example syntax for overriding broken spanners, context-id-specific overrides, etc. The first run of GLISS will probably not involve any tweaks or overrides, but we'll see how it goes. What do you mean by tweaks and overrides? The syntax of these commands itself, i.e. whether we should require #s or not? I have an idea about syntax that would affect bot regular and tweak syntax, and it doesn't make much sense to discuss it in two parts because the logical connection would be lost. cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc build hanging (with memory leak?)
Joseph, On 12 May 2012 12:56, Joseph Rushton Wakeling joseph.wakel...@webdrake.net wrote: On 12/05/12 13:37, David Kastrup wrote: You are running a command - echo texi2html not found and that does not quite work. It would appear that the error handling for a missing texi2html script is totally awful. I'd install texi2html and rerun configure. Texi2html was already installed, but re-running configure revealed that dblatex was missing (for some reason aptitude build-dep lilypond didn't include that). Seems to be working now (can't be certain, it's still building:-). Assuming you are building from current master then make doc does compile as all new checkins go to staging tree first and sit there while a script runs (as it happens on my computer) that compiles staging through all the tests and if it passes them all (and that includes a make doc) it merges the staging branch to master. So you can pretty much safely assume that master is compilable, and that any issues you have are probably down to the need to simple make clean, re-rerun autogen.sh and configure then make and so on. My only advice having built docs and gone through all the pain of a non-programmer building doc is to use an out of tree build (i.e. make a build dir in your lilypond repository, run ./autogen.sh --noconfigure outside of the build dir, then cd into it and run ../configure; make ; make doc that way. If you get any odditites you can simply rm your build and start again without worrying too much about if you have made a mess of your tree and make clean is not working. This is all mentioned (if you are not already doing this) here: http://lilypond.org/doc/v2.15/Documentation/contributor/compiling-with-lilydev and although this is for specifically using the Ubuntu based iso we have available, the same principles apply. I've found it makes this so much more easier especially when you have a slower machine where make doc can take an age. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
On Sat, May 12, 2012 at 12:51 PM, m...@apollinemike.com m...@apollinemike.com wrote: I wouldn't mind using it to finish my skyline work! That'll easily be five weeks of my life (around 1 000 €), and it'd allow me to focus on something other than fundraising... I'm ok with this, too! Let's see what others will propose, however. Btw, if anyone has trouble finding an issue that is both interesting to him and has appropriate size, i can come up with some project ideas. congratulations again, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
The jury wishes to congratulate you on your LilyPond open source software, that won the First Prize at the LoMus 2012 contest. Great! Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
On 12 mai 2012, at 14:38, Janek Warchoł wrote: On Sat, May 12, 2012 at 12:51 PM, m...@apollinemike.com m...@apollinemike.com wrote: I wouldn't mind using it to finish my skyline work! That'll easily be five weeks of my life (around 1 000 €), and it'd allow me to focus on something other than fundraising... if anyone has trouble finding an issue that is both interesting to him, Or her. Just saying. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: LoMus 2012
On Sat, May 12, 2012 at 12:37 PM, David Kastrup d...@gnu.org wrote: Make a ponding of the award, and point to the contest site (if any) for the details. Like the awarded sum. I'd find it weird to flash numbers on our main website. I think this qualifies for a news item - after all, it's *LilyPond* who won. Graham? Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
On 12 mai 2012, at 14:53, Janek Warchoł wrote: On Sat, May 12, 2012 at 12:37 PM, David Kastrup d...@gnu.org wrote: Make a ponding of the award, and point to the contest site (if any) for the details. Like the awarded sum. I'd find it weird to flash numbers on our main website. I think this qualifies for a news item - after all, it's *LilyPond* who won. Graham? I completely agree. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
On 5/12/12 4:37 AM, David Kastrup d...@gnu.org wrote: m...@mikesolomon.org m...@mikesolomon.org writes: w00t! Mazal tov to everyone! Graham's worst fears... If I remember correctly, we had two applications for the Google Summer of Code, and only one has been accepted under the GNU umbrella. Before dispersion fights start, it might make sense asking the other applicant whether an admittedly smaller sum like this might enable him to embark on his project or part of it. The other applicant appears to not be a serious applicant. He has not even spoken up on -user or -devel to get to know anything about lilypond. I don't think he should be part of this equation. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc build hanging (with memory leak?)
On 12/05/12 14:29, James wrote: Assuming you are building from current master then make doc does compile as all new checkins go to staging tree first and sit there while a script runs (as it happens on my computer) that compiles staging through all the tests and if it passes them all (and that includes a make doc) it merges the staging branch to master. Yea, it built fine in the end once dblatex was installed. It was just scary having an initial command issued by make which just sat there for 10+ minutes doing nothing while the memory usage went up and up. Completely different to what I'd experienced with earlier builds of the docs. A small word to this effect might be a nice addition to the contributor guide (I'll make a patch if you like). My only advice having built docs and gone through all the pain of a non-programmer building doc is to use an out of tree build Yes, I followed that advice from the guide. Is it a recent addition? I don't remember it from the last time I looked at the guide, which was probably 6+ months back. I've found it makes this so much more easier especially when you have a slower machine where make doc can take an age. On my quad-core i7 it took about 35 minutes in total to build doc-stage-1, the first 10-12 minutes of which were the seeming hang I reported. I remember it used to take much, much, much longer on the machine I had 6 months back, but there was plenty flashing past in the terminal window to make it clear something was happening! If I understand right, that first documentation build command is making all the PNG, PS and PDF files for LP snippets -- right? -- which if my estimation is correct are a bit over 10,000 in number. So no wonder it takes so long. Thanks to all for your advice and explanations. :-) -- Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
David Kastrup writes: Well, I was going to send news of it around, but as of now, there is nothing to be seen yet: URL:http://concours.afim-asso.org/home.php. Hope they get their act together eventually, since this is definitely nice promotion material. /me too; please update when there's a website with info available. I haven't seen anything besides https://twitter.com/#!/kyojindo/status/200967005380165633 which is also not too official. Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
On 12 mai 2012, at 15:55, David Kastrup wrote: Jan Nieuwenhuizen jann...@gnu.org writes: David Kastrup writes: Well, I was going to send news of it around, but as of now, there is nothing to be seen yet: URL:http://concours.afim-asso.org/home.php. Hope they get their act together eventually, since this is definitely nice promotion material. /me too; please update when there's a website with info available. I haven't seen anything besides https://twitter.com/#!/kyojindo/status/200967005380165633 which is also not too official. Hm. Taking a look at Pyo, the second prize, and speculating about its mindshare, I have the suspicion that LilyPond has more or less been the proverbial 500lb Gorilla in the contest. This is not untrue, but I think somebody submit PD to LoMuS a few years back, so it really depends. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1050
Documentation/notation/input.itely:1050: is to be attached but in that
case, it must be preceded by a @code{};
Seems like I caused you unnecessary work by being unclear. I am sorry
for that. is a stopgap measure created by convert-ly since automatic
change to postevent position of the real event is not feasible.
\footnote should be documented as purely being a postevent, and the
examples should be changed accordingly from the state after automatic
conversion. Any explanation of or s1*0 belongs in a different part
of the manual generally talking about how to deal with postevents you
have no anchor for.
The state after the automatic conversion is not really acceptible in
documentation: it only has the advantage of maintaining functionality.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1059
Documentation/notation/input.itely:1059: \footnote #'(0.5 . -2)
#'NoteHead
So this, for example, should be changed to
a'4\footnote #'(0.5 . -2) #'NoteHead
\markup { The first note }
b8 e\footnote #'(0.5 , 1) #'NoteHead
\markup { The third note }
c4
and so on.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1068
Documentation/notation/input.itely:1068: % Chorded Notes
Notes inside of a chord can be given individual footnotes. or
something like this should be mentioned.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1072
Documentation/notation/input.itely:1072: g\footnote #'(2 . 2) \markup {
\bold This is a G }
Visual correction here?
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1089
Documentation/notation/input.itely:1089: \footnote #'(-3 . 0)
#'DynamicText
Doesn't this give an error? The footnotes are not in postevent
position. I think they would need to move after a'4. Similar for the
following notes.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1138
Documentation/notation/input.itely:1138: Like automatic footnotes, the
@code{\footnote} command can be placed
See above: I'd not mention at all.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1148
Documentation/notation/input.itely:1148: \footnote
Now I am baffled. Reintroducing manually? Or was this copypaste
for some reason?
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1177
Documentation/notation/input.itely:1177: \footnote
See above. I should be surprised if this works unless you move the
\footnote after a'4.
http://codereview.appspot.com/6137050/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: LoMus 2012
Janek Warchoł writes: I think this qualifies for a news item - after all, it's *LilyPond* who won. Graham? Submit to lwn.net etc; when there's something to point at. Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc build hanging (with memory leak?)
On Sat, May 12, 2012 at 01:56:33PM +0200, Joseph Rushton Wakeling wrote: On 12/05/12 13:37, David Kastrup wrote: and that does not quite work. It would appear that the error handling for a missing texi2html script is totally awful. I'd install texi2html and rerun configure. Texi2html was already installed, but re-running configure revealed that dblatex was missing (for some reason aptitude build-dep lilypond didn't include that). huh, thanks for the report. http://code.google.com/p/lilypond/issues/detail?id=2529 - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc build hanging (with memory leak?)
hello, On 12 May 2012 14:24, Joseph Rushton Wakeling joseph.wakel...@webdrake.net wrote: On 12/05/12 14:29, James wrote: Assuming you are building from current master then make doc does compile as all new checkins go to staging tree first and sit there while a script runs (as it happens on my computer) that compiles staging through all the tests and if it passes them all (and that includes a make doc) it merges the staging branch to master. Yea, it built fine in the end once dblatex was installed. It was just scary having an initial command issued by make which just sat there for 10+ minutes doing nothing while the memory usage went up and up. Completely different to what I'd experienced with earlier builds of the docs. A small word to this effect might be a nice addition to the contributor guide (I'll make a patch if you like). Sure go ahead. My only advice having built docs and gone through all the pain of a non-programmer building doc is to use an out of tree build Yes, I followed that advice from the guide. Is it a recent addition? I don't remember it from the last time I looked at the guide, which was probably 6+ months back. Not sure, but the CG is constantly changing, or rather constantly being 'added' to and evolving. There have been *significant* under-the-hood changes to the whole build system not least Phil's work on reducing the sheer number of output lines - I recall that you can increase the logging if you want to (I don't and haven't bothered to look that up in he CG to see if it exists but I think it does) - and some issues with translations that caused extraneous/erroneous errors that would increase the time it takes to build doc. You can also now use the LANG option to just build the language you need (again see the CG). I've found it makes this so much more easier especially when you have a slower machine where make doc can take an age. On my quad-core i7 it took about 35 minutes in total to build doc-stage-1, the first 10-12 minutes of which were the seeming hang I reported. I remember it used to take much, much, much longer on the machine I had 6 months back, but there was plenty flashing past in the terminal window to make it clear something was happening! Yes and most of it was warnings and errors that were 'harmless'. Most of the heavy lifting with regard to fixing this was done by multi-core CPU machines (Phil and myself) which have helped take the tedium of checking building doc and the like allowing for much more 'quick' testing of fixes to the build system - we both manage build a brand new make doc from scratch in less than 15 minutes! So can forget sometimes what building doc looks like on a less powered machine. If I understand right, that first documentation build command is making all the PNG, PS and PDF files for LP snippets -- right? -- which if my estimation is correct are a bit over 10,000 in number. So no wonder it takes so long. Something like that yes. As a non-programmer I just 'test' what is done and give the results. I don't pretend to understand what the changes are ;) Regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: LoMus 2012
On Sat, May 12, 2012 at 02:53:58PM +0200, Janek Warchoł wrote: On Sat, May 12, 2012 at 12:37 PM, David Kastrup d...@gnu.org wrote: Make a ponding of the award, and point to the contest site (if any) for the details. Like the awarded sum. I'd find it weird to flash numbers on our main website. I think this qualifies for a news item - after all, it's *LilyPond* who won. Graham? sure. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilipond's web site update suggestion (Frescobaldi compatible platforms)
Hello, On 12 May 2012 16:41, Graham Percival gra...@percival-music.ca wrote: Hi Marc, Thanks for the report! James: could you either make this change yourself (after double-checking the details), or add a tracker item for it? I think you can push this directly. Thanks Marc. This has now been fixed and will be incorporated in the next website build @Graham I didn't make a tracker. committer James Lowe pkx1...@gmail.com Sat, 12 May 2012 16:12:29 + (17:12 +0100) commit 78a723022056dd2b3e09edcbee76d0a49ced4d6c Thanks James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMus 2012
On Sat, May 12, 2012 at 8:02 AM, m...@apollinemike.com m...@apollinemike.com wrote: I wouldn't mind using it to finish my skyline work! That'll easily be five weeks of my life (around 1 000 €), and it'd allow me to focus on something other than fundraising... Well, the agreement was whoever submits and collects, decides how to distribute, and I doubt anybody would be adverse to good skylines. Figure in another five weeks for dealing with requests for code documentation and another five for dealing with regressions, and you are not exactly going to end up ahead, anyway. This is not untrue... :) Bottom line - CONGRATS TO EVERYONE. This is the most prestigious open-source music software competition in the world. Get excited! Congrats to everyone, including myself! (isnt it the *only* open-source music software competition in the world? :-) -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)
See inline. One more patch will be needed.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1050
Documentation/notation/input.itely:1050: is to be attached but in that
case, it must be preceded by a @code{};
On 2012/05/12 14:25:08, dak wrote:
Seems like I caused you unnecessary work by being unclear. I am sorry
for that.
is a stopgap measure created by convert-ly since automatic change
to
postevent position of the real event is not feasible.
Ah ok. I see. I.e. you cannot make convert-ly change where the
'\footnote' command 'string' is in the .ly file so in this pre-event(?)
you just stick in place so it works.
\footnote should be documented as purely being a postevent, and the
examples
should be changed accordingly from the state after automatic
conversion. Any
explanation of or s1*0 belongs in a different part of the manual
generally
talking about how to deal with postevents you have no anchor for.
OK.
The state after the automatic conversion is not really acceptible in
documentation: it only has the advantage of maintaining functionality.
Yes I see now.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1059
Documentation/notation/input.itely:1059: \footnote #'(0.5 . -2)
#'NoteHead
On 2012/05/12 14:25:08, dak wrote:
So this, for example, should be changed to
a'4\footnote #'(0.5 . -2) #'NoteHead
\markup { The first note }
b8 e\footnote #'(0.5 , 1) #'NoteHead
\markup { The third note }
c4
and so on.
Done.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1068
Documentation/notation/input.itely:1068: % Chorded Notes
On 2012/05/12 14:25:08, dak wrote:
Notes inside of a chord can be given individual footnotes. or
something like
this should be mentioned.
I've reworded it to be less specific than that. But the examples and the
new text should now indicate this fact more clearly than before.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1072
Documentation/notation/input.itely:1072: g\footnote #'(2 . 2) \markup {
\bold This is a G }
On 2012/05/12 14:25:08, dak wrote:
Visual correction here?
Yes. I thought the indicator was too close to the measure 'above' - its
an a8 page size remember? This show the footnotes at the 'bottom' of the
page without needing huge space (for bigger page size), so you only get
one measure per line. Unless you compile this example I can see how this
correction might not make sense.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1089
Documentation/notation/input.itely:1089: \footnote #'(-3 . 0)
#'DynamicText
On 2012/05/12 14:25:08, dak wrote:
Doesn't this give an error? The footnotes are not in postevent
position. I
think they would need to move after a'4. Similar for the following
notes.
Yes you are correct. Thanks for spotting. I ran all (or thought 'all')
the example through a lilypond-book template that I have, one at a time,
so I could tweak-and-fiddle examples quickly - without having to build
the whole doc. I obviously missed this one!
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1138
Documentation/notation/input.itely:1138: Like automatic footnotes, the
@code{\footnote} command can be placed
On 2012/05/12 14:25:08, dak wrote:
See above: I'd not mention at all.
Done.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1148
Documentation/notation/input.itely:1148: \footnote
On 2012/05/12 14:25:08, dak wrote:
Now I am baffled. Reintroducing manually? Or was this copypaste
for some
reason?
Sigh - sorry. The was left in (because I didn't understand the post
event thing you discussed above. The rest of the example was when I
noticed that some lines caused the ugly black bars to appear in the PDF
output (when your line length exceeds certain length) so again I had to
fiddle-and-tweak the example to remove those.
Hopefully it is ok now.
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1177
Documentation/notation/input.itely:1177: \footnote
On 2012/05/12 14:25:08, dak wrote:
See above. I should be surprised if this works unless you move the
\footnote
after a'4.
Yes again, it was simply going up and down in the texi file that I
missed this.
However I now cannot work out how to footnote the '\breathe' mark as
wherever I put the \breathe command I get an error. I have left it in
for now commented out in case this is simply not understanding where it
goes, or if this is a change in the footnote behaviour since this code
change.
This is different from the above example because I think that manual
Re: Add mail aliases for Carl, Colin, Janek, and Pál, for the sake of git shortlog (issue 6206057)
Reviewers: Graham Percival, Message: On 2012/05/12 17:08:25, Graham Percival wrote: LGTM, I think this can be pushed immediately to staging. Willdo. Description: Add mail aliases for Carl, Colin, Janek, and Pál, for the sake of git shortlog Please review this at http://codereview.appspot.com/6206057/ Affected files: M .mailmap Index: .mailmap diff --git a/.mailmap b/.mailmap index ac9bad10287b1bc6e11547a5c74d5f1d12c622eb..a8ae3180ee8e9461f7c339ce3e30abafa74cf437 100644 --- a/.mailmap +++ b/.mailmap @@ -2,10 +2,13 @@ Andrew Hawryluk ahawry...@gmail.com Andrew Hawryluk andrew@obi-wan.(none) Andrew Wilson and...@rivendale.net Arjan Bos arjan@hetnet.nl +Benkő Pál benko@gmail.com Boris Shingarov b...@shingarov.com Boris Shingarov shinga...@gmail.com Carl D. Sorensen carldsorensen Carl D. Sorensen c_soren...@byu.edu +Carl D. Sorensen carl.d.soren...@gmail.com +Colin Campbell colinpkcampb...@gmail.com Chris Snyder csny...@adoromusicpub.com Damien Heurtebise famille.heurteb...@free.fr Daniel Johnson il.basso.bu...@gmail.com @@ -102,6 +105,9 @@ James Lowe james@james-lilybunto.(none) James Lowe james@james-lily.(none) James Lowe james.l...@datacore.com James Lowe jlowe@james-ubuntu.(none) +Janek Warchoł janek.lilyp...@gmail.com +Janek Warchoł lemniskata.bernoull...@gmail.com +Janek Warchoł lemniskata.bernoulli...@gmail.com Jan Nieuwenhuizen jan Jan Nieuwenhuizen janneke Jan Nieuwenhuizen jann...@gnu.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)
Looks good to me.
I honestly tried to use a footnote a couple months ago, but gave up
trying to figure it out. Now I think the docs are pretty clear.
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1044
Documentation/notation/input.itely:1044: Automatic footnotes take three
arguments; the @var{Layout Object} to be
maybe Automatically-numbered footnotes
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1076
Documentation/notation/input.itely:1076: higher up in the list.}
Do you mean that footnotes on the same chord are numbered and listed in
order the vertical positions of their indicators, G Eb C ? If that is
it, you might want it in normal text rather than a warning.
(I had to look up 'descendancy', so my problem might have just been my
English comprehension.)
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1128
Documentation/notation/input.itely:1128: Manual footnotes takes four
arguments; the @var{Layout Object} to be
maybe Footnotes with manually-chosen indicators take
and in any case, take
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1159
Documentation/notation/input.itely:1159: higher up in the list.}
From experiment, it seems that, a set of footnotes on one chord are
listed at the bottom of the page according to the vertical order of
their indicators. -- which is quite nice.
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1181
Documentation/notation/input.itely:1181:
Works for me to put here, \breathe
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1185
Documentation/notation/input.itely:1185: \markup { \bold 4. { This is a
stem } }
and then here
\footnote
\markup { \teeny \musicglyph #rests.4 }
#'(-0.5 . 0.5) #'BreathingSign
\markup { \null }
In rhythms were you usually see a breath mark, it is printed just before
the next note. Breathing just after two eight notes is a little odd,
but it would take some re-arranging of the example to make it realistic,
and maybe not worth it.
http://codereview.appspot.com/6137050/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)
On 2012/05/12 18:36:56, Keith wrote:
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1073
Documentation/notation/input.itely:1073: 1
2
\breathe
c2
\footnote #'(0.5 . 0.5) #'BreathingSign \markup { Breathe }
The \breathe example is more normal-looking here.
Not exactly the most intuitive order I have to say. \breathe does not
take a postevent, though, so the alternative would be the use of
\footnote or equivalent, either before or after \breathe itself:
\breathe creates an event without duration.
This is one case where the postevent order is not helpful, because the
thing you want to modify itself does not take a postevent. Putting the
postevent on c2 instead delivers it at the right point of time, but this
is plainly counterintuitive.
http://codereview.appspot.com/6137050/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)
On 2012/05/12 19:11:44, dak wrote:
On 2012/05/12 18:36:56, Keith wrote:
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1073
Documentation/notation/input.itely:1073: 1
2
\breathe
c2
\footnote #'(0.5 . 0.5) #'BreathingSign \markup { Breathe }
The \breathe example is more normal-looking here.
Not exactly the most intuitive order I have to say. \breathe does not
take a
postevent, though, so the alternative would be the use of
\footnote or equivalent, either before or after \breathe itself:
\breathe creates an event without duration.
This is one case where the postevent order is not helpful, because the
thing you
want to modify itself does not take a postevent. Putting the
postevent on c2
instead delivers it at the right point of time, but this is plainly
counterintuitive.
c2
\footnote #'(0.5 . 0.5) #'BreathingSign \markup { Breathe }
-\breathe
does work: turning \breathe explicitly into a postevent makes the
arrangement in toto somewhat more natural, even though having the
\breathe after the note is a bit surprising.
But a bit less jarring than the alternative.
http://codereview.appspot.com/6137050/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)
On 2012/05/12 19:25:34, dak wrote:
On 2012/05/12 19:11:44, dak wrote:
On 2012/05/12 18:36:56, Keith wrote:
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/11001/Documentation/notation/input.itely#newcode1073
Documentation/notation/input.itely:1073: 1
2
\breathe
c2
\footnote #'(0.5 . 0.5) #'BreathingSign \markup { Breathe }
The \breathe example is more normal-looking here.
Not exactly the most intuitive order I have to say. \breathe does
not take a
postevent, though, so the alternative would be the use of
\footnote or equivalent, either before or after \breathe itself:
\breathe creates an event without duration.
This is one case where the postevent order is not helpful, because
the thing
you
want to modify itself does not take a postevent. Putting the
postevent on c2
instead delivers it at the right point of time, but this is plainly
counterintuitive.
c2
\footnote #'(0.5 . 0.5) #'BreathingSign \markup { Breathe }
-\breathe
does work: turning \breathe explicitly into a postevent makes the
arrangement in
toto somewhat more natural, even though having the \breathe after the
note is a
bit surprising.
But a bit less jarring than the alternative.
Sigh. I take that back. It is more or less a historical accident that
\breathe is defined as a music function (and thus can be used in the
place of an explicit postevent). The purported reason told in comments
in music-function-init.ly for that redefinition does not exist anymore,
and the plainer replacement
breathe = #(make-music 'BreathingEvent)
does not work as postevent, so comparable expressions would also not
work.
That's really starting to look like a case for \footnote or
equivalent. Or leave it like Keith proposed.
http://codereview.appspot.com/6137050/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)
On Sat, 12 May 2012 12:11:45 -0700, d...@gnu.org wrote:
\breathe
c2
\footnote #'(0.5 . 0.5) #'BreathingSign \markup { Breathe }
Not exactly the most intuitive order I have to say.
True. Good to document it, I guess.
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1049
Documentation/notation/input.itely:1049: The @code{\footnote} command
comes immediately after the item being
... comes after the note or rest associated with the item being
annotated
to be more accurate for the odd things like the breath mark. And as you
show later, if you have dynamics and a slur on a sharped note, you can
type the \footnote for the sharp after \f( -- which might be convenient.
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1069
Documentation/notation/input.itely:1069: 1
maybe bring the example for #'Accidental up here, too, where there is
more space in the typeset output ?
1
\breathe
cis2
\footnote #'(0.5 . 0.5) #'BreathingSign \markup { Gasp}
\footnote #'(0.5 , 0.5) #'Accidental \markup { Chromatic }
http://codereview.appspot.com/6137050/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)
New patch set uploaded
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1044
Documentation/notation/input.itely:1044: Automatic footnotes take three
arguments; the @var{Layout Object} to be
On 2012/05/12 18:23:23, Keith wrote:
maybe Automatically-numbered footnotes
This made me re-think the titling of both these sections, so I have
re-titled them to something more descriptive and adjusted the body text
accordingly.
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1049
Documentation/notation/input.itely:1049: The @code{\footnote} command
comes immediately after the item being
On 2012/05/12 21:01:35, Keith wrote:
... comes after the note or rest associated with the item being
annotated
to be more accurate for the odd things like the breath mark. And as
you show
later, if you have dynamics and a slur on a sharped note, you can type
the
\footnote for the sharp after \f( -- which might be convenient.
Done.
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1069
Documentation/notation/input.itely:1069: 1
On 2012/05/12 21:01:35, Keith wrote:
maybe bring the example for #'Accidental up here, too, where there is
more space
in the typeset output ?
1
\breathe
cis2
\footnote #'(0.5 . 0.5) #'BreathingSign \markup { Gasp}
\footnote #'(0.5 , 0.5) #'Accidental \markup { Chromatic }
Done. Thanks.
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1076
Documentation/notation/input.itely:1076: higher up in the list.}
On 2012/05/12 18:23:23, Keith wrote:
Do you mean that footnotes on the same chord are numbered and listed
in order
the vertical positions of their indicators, G Eb C ? If that is it,
you might
want it in normal text rather than a warning.
(I had to look up 'descendancy', so my problem might have just been my
English
comprehension.)
Done.
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1076
Documentation/notation/input.itely:1076: higher up in the list.}
On 2012/05/12 18:23:23, Keith wrote:
Do you mean that footnotes on the same chord are numbered and listed
in order
the vertical positions of their indicators, G Eb C ?
If it is a chord yes, but you can have multiple 'grobs' that are not in
chords but come at the same vertical position too. I am not sure now.
Mike's turn of phrase might have been ambiguous when giving me answers
to questions on footnotes when I was writing this up but he might have
meant the same 'moment' in this case, but I am not sure if this is
1. Correct technically
2. Same vertical position is, in this context, synonymous with same
'moment' on the staff or not.
3. If it is do we want to get into explaining 'moments' in this case?
If that is it, you might
want it in normal text rather than a warning.
(I had to look up 'descendancy', so my problem might have just been my
English
comprehension.)
I removed the @warning, and used a simpler phrase, that will also make
for easier translation in the other languages.
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1128
Documentation/notation/input.itely:1128: Manual footnotes takes four
arguments; the @var{Layout Object} to be
On 2012/05/12 18:23:23, Keith wrote:
maybe Footnotes with manually-chosen indicators take
I've changed this based on the new section heading.
and in any case, take
Done. (and also in the automatically numbered section too)
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1159
Documentation/notation/input.itely:1159: higher up in the list.}
On 2012/05/12 18:23:23, Keith wrote:
From experiment, it seems that, a set of footnotes on one chord are
listed at
the bottom of the page according to the vertical order of their
indicators. --
which is quite nice.
I've changed this wording as per the automatically numbered section too.
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1181
Documentation/notation/input.itely:1181:
On 2012/05/12 18:23:23, Keith wrote:
Works for me to put here, \breathe
Done.
http://codereview.appspot.com/6137050/diff/8003/Documentation/notation/input.itely#newcode1185
Documentation/notation/input.itely:1185: \markup { \bold 4. { This is a
stem } }
On 2012/05/12 18:23:23, Keith wrote:
and then here
\footnote
\markup { \teeny \musicglyph #rests.4 }
#'(-0.5 . 0.5) #'BreathingSign
\markup { \null }
In rhythms were you usually see a breath mark, it is printed just
before the
next note.
I guess I don't see that in my own music, I picked up a few random
scores and they all came at or on the bar line.
Breathing just after two eight
Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)
Big change, still very clear.
http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely#newcode1048
Documentation/notation/input.itely:1048: the order in which each
indicator, and so footnotes, are created during
each... footnote is
http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely#newcode1075
Documentation/notation/input.itely:1075: \footnote #'(0.5 , 0.5)
#'Accidental \markup { Chromatic }
r2
to square up the bar
http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely#newcode1080
Documentation/notation/input.itely:1080: When footnotes have the same
vertical position they are printed in
In this case, maybe the word moment is best :
When several footnotes mark items at the same moment in the music, they
are printed...
http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely#newcode1144
Documentation/notation/input.itely:1144: are created during compilation.
each.. is
http://codereview.appspot.com/6137050/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Fix ukulele tunings (issue 6206060)
Reviewers: , Message: tenor-ukulele-tuning and baritone-ukulele-tuning fixed, the string order was reversed. Description: Fix ukulele tunings Reverse the order of the chord for the tenor-ukulele-tuning and baritone-ukulele-tuning Please review this at http://codereview.appspot.com/6206060/ Affected files: M ly/string-tunings-init.ly Index: ly/string-tunings-init.ly diff --git a/ly/string-tunings-init.ly b/ly/string-tunings-init.ly index b4259a8410a9acad6491db5e082a4587ad589c4a..a003a1e4921de89a27d6fe97c75215c801d6a82b 100644 --- a/ly/string-tunings-init.ly +++ b/ly/string-tunings-init.ly @@ -75,8 +75,8 @@ for documentation purposes.) %% ukulele tunings \makeDefaultStringTuning #'ukulele-tuning \stringTuning g' c' e' a' \makeDefaultStringTuning #'ukulele-d-tuning \stringTuning a' d' fis' b' -\makeDefaultStringTuning #'tenor-ukulele-tuning \stringTuning a' e' c' g -\makeDefaultStringTuning #'baritone-ukulele-tuning \stringTuning e' b g d +\makeDefaultStringTuning #'tenor-ukulele-tuning \stringTuning g c' e' a' +\makeDefaultStringTuning #'baritone-ukulele-tuning \stringTuning d g b e' %% orchestral strings \makeDefaultStringTuning #'violin-tuning \stringTuning g d' a' e'' ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: NR clarified \footnote command as a TextScript (issue 6137050)
http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/14003/Documentation/notation/input.itely#newcode1075
Documentation/notation/input.itely:1075: \footnote #'(0.5 , 0.5)
#'Accidental \markup { Chromatic }
Eek! Comma in place of a dot!
My typo, but never trust me with Scheme. Silly programming language
with all its picky distinctions between tiny bits of punctuation.
http://codereview.appspot.com/6137050/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Use fractions rather than Scheme pairs for \scaleDuration, timeSignatureFraction et al (issue 6200068)
http://codereview.appspot.com/6200068/diff/2001/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
http://codereview.appspot.com/6200068/diff/2001/Documentation/notation/rhythms.itely#newcode331
Documentation/notation/rhythms.itely:331: a4*2/3 gis a
Oh yes. You had asked who were some people who use this construction.
It's not just me this time; I also see it in other people's scores on
mutopiaproject.
I'll admit that I used it to avoid the Lisp syntax in \scaleDurations
#'(2 . 3)
http://codereview.appspot.com/6200068/diff/2001/Documentation/snippets/new/changing-time-signatures-inside-a-polymetric-section-using--scaledurations.ly
File
Documentation/snippets/new/changing-time-signatures-inside-a-polymetric-section-using--scaledurations.ly
(right):
http://codereview.appspot.com/6200068/diff/2001/Documentation/snippets/new/changing-time-signatures-inside-a-polymetric-section-using--scaledurations.ly#newcode25
Documentation/snippets/new/changing-time-signatures-inside-a-polymetric-section-using--scaledurations.ly:25:
\scaleDurations 8/5 {
Somehow, this worked before the patch. Not a problem, just an
observation.
http://codereview.appspot.com/6200068/diff/2001/lily/lexer.ll
File lily/lexer.ll (right):
http://codereview.appspot.com/6200068/diff/2001/lily/lexer.ll#newcode487
lily/lexer.ll:487: {FRACTION} {
Stupid question, but I can't figure it out. Can we remove this pattern
from the rules for individual starting states, now that it is matched
globally ?
http://codereview.appspot.com/6200068/diff/2001/lily/lexer.ll#newcode528
lily/lexer.ll:528: {FRACTION} {
?
http://codereview.appspot.com/6200068/diff/2001/lily/lexer.ll#newcode573
lily/lexer.ll:573: {FRACTION} {
?
http://codereview.appspot.com/6200068/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fix ukulele tunings (issue 6206060)
On 2012/05/13 02:29:54, choan.galvez wrote: tenor-ukulele-tuning and baritone-ukulele-tuning fixed, the string order was reversed. In the user group, a more extensive change was/is discussed that could also be worthwhile. This patch here, in contrast, is just a bug fix. As such, applying it is a no-brainer. I'd push it to staging right after it passes the standard test (and I should be rather shocked if it did not). http://codereview.appspot.com/6206060/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Use fractions rather than Scheme pairs for \scaleDuration, timeSignatureFraction et al (issue 6200068)
Reviewers: Keith,
http://codereview.appspot.com/6200068/diff/2001/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
http://codereview.appspot.com/6200068/diff/2001/Documentation/notation/rhythms.itely#newcode331
Documentation/notation/rhythms.itely:331: a4*2/3 gis a
On 2012/05/13 02:43:23, Keith wrote:
Oh yes. You had asked who were some people who use this
construction. It's
not just me this time; I also see it in other people's scores on
mutopiaproject.
I'll admit that I used it to avoid the Lisp syntax in \scaleDurations
#'(2 . 3)
\scaleDurations 2/3 would have worked from version 2.15.17 on (fractions
in function arguments). The necessity of parser changes to allow for
fractions in property initializations caught me on the wrong foot: I
would have imagined the first patch set to work already. This was
supposed to be just a documentation change.
http://codereview.appspot.com/6200068/diff/2001/Documentation/snippets/new/changing-time-signatures-inside-a-polymetric-section-using--scaledurations.ly
File
Documentation/snippets/new/changing-time-signatures-inside-a-polymetric-section-using--scaledurations.ly
(right):
http://codereview.appspot.com/6200068/diff/2001/Documentation/snippets/new/changing-time-signatures-inside-a-polymetric-section-using--scaledurations.ly#newcode25
Documentation/snippets/new/changing-time-signatures-inside-a-polymetric-section-using--scaledurations.ly:25:
\scaleDurations 8/5 {
On 2012/05/13 02:43:23, Keith wrote:
Somehow, this worked before the patch. Not a problem, just an
observation.
Yup. As I said: 2.15.17 for function arguments (that's when \times 2/3
... became a regular function instead of a reserved word in the parser).
http://codereview.appspot.com/6200068/diff/2001/lily/lexer.ll
File lily/lexer.ll (right):
http://codereview.appspot.com/6200068/diff/2001/lily/lexer.ll#newcode487
lily/lexer.ll:487: {FRACTION} {
On 2012/05/13 02:43:23, Keith wrote:
Stupid question, but I can't figure it out. Can we remove this
pattern from the
rules for individual starting states, now that it is matched globally
?
I have not tried it. We have separate rules for unsigned, possibly
because 3.5 can means something else in some modes. One should probably
make sure that in special situations, like figured bass or chordmode,
the global parser change does not cause trouble.
I have not really given it any thought yet, relying on the regtests to
tell me if I was hitting on the syntax of existing constructs.
If one tried simplifying this, one should make sure that rules still
back up.
Description:
Use fractions rather than Scheme pairs for \scaleDuration,
timeSignatureFraction et al
Please review this at http://codereview.appspot.com/6200068/
Affected files:
M Documentation/ly-examples/aucun-snippet.ly
M Documentation/notation/rhythms.itely
A
Documentation/snippets/new/changing-time-signatures-inside-a-polymetric-section-using--scaledurations.ly
M input/regression/chord-tremolo-scaled-durations.ly
M input/regression/time-signature-settings-by-staff.ly
M lily/lexer.ll
M lily/parser.yy
M ly/engraver-init.ly
M ly/performer-init.ly
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
