Re: Mentions separate build directory for website work (issue 6092045)
On 2012/04/27 15:01:23, mike7 wrote: I think the problem is that it tries to do a blanket copy of everything from the misc directory into the target directory, but if the build is not in a separate build directory, then there will be out/ in misc, which is a directory. Sounds like it could use an --exclude, then. Or a more explicit listing of files in misc/. http://codereview.appspot.com/6092045/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
On Fri, Apr 27, 2012 at 11:14:23AM +0200, David Kastrup wrote: Graham Percival gra...@percival-music.ca writes: Then we'll have hard numbers on which developers are abusing the process. I mean, sure, we all know whose patches tend to be great and whose patches tend to be problematic... but a completely automated, objective approach would remove any personal bias. And those who generated more negative karma with their work than the average horse in the stables near our house will get banished from contributing for two weeks? No; I'm expecting the Hawthorne effect to take care of it. Get real. When the cure is worse than the symptom, leave it alone. Well, that would be the question. If programmers know that there will be a record of any bad patch submissions, would they be less likely to contribute? Or would they be more likely to check their work before submitting it? I'm obviously hoping for the latter, but I suppose that the former is still a logical possibility. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMuS
On Fri, Apr 27, 2012 at 08:26:16AM +0200, m...@apollinemike.com wrote: On 27 avr. 2012, at 08:07, Graham Percival wrote: On Fri, Apr 27, 2012 at 07:09:39AM +0200, m...@apollinemike.com wrote: I'd be good to set a precedent for this now so that LilyPond can apply to other software competitions in the future. *sigh* I'll formulate my question differently. If anyone on the development team sends me an e-mail saying Do not submit LilyPond to LoMuS, I won't submit LilyPond to LoMuS. So... you *don't* want to set a precedent; you just want a quick answer about this specific case? I guess the general consensus is go ahead and we'll figure it out later. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
assistant release manger
Given how things are going, it's past time that we have somebody else that can make releases. Who's interested in learning? Requirements: - powerful computer - can already compile GUB from scratch - is well known to lilypond developers (say, at least 1 year of lilypond development) - familiar with ssh, unix shell scripts, and python scripts If you are a candidate but feel that you are too busy working on other lilypond stuff, then findtrain a replacement for that stuff over the next few weeks so you can do releases. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMuS
On 28 avr. 2012, at 09:15, Graham Percival wrote: On Fri, Apr 27, 2012 at 08:26:16AM +0200, m...@apollinemike.com wrote: On 27 avr. 2012, at 08:07, Graham Percival wrote: On Fri, Apr 27, 2012 at 07:09:39AM +0200, m...@apollinemike.com wrote: I'd be good to set a precedent for this now so that LilyPond can apply to other software competitions in the future. *sigh* I'll formulate my question differently. If anyone on the development team sends me an e-mail saying Do not submit LilyPond to LoMuS, I won't submit LilyPond to LoMuS. So... you *don't* want to set a precedent; you just want a quick answer about this specific case? I guess the general consensus is go ahead and we'll figure it out later. I *do* want this to work so well that it sets a solid precedent, but I think that a lot of times a ball can get rolling on a precedent with a quick answer about a specific case. I get the sense in a way that the precedent has already been set - if someone sees a cool opportunity (GSoC, LoMuS, whatever), email the list to call dibs if dibs must be called, make sure no one is opposed, apply, and do something fair with the money if money is to be gotten. In the GSoC case, Janek has $500 that he'll be donating to the organization in whatever way he sees fit. In the Lomus case, if that works out, I'll have 3000 € and will do the same. This seems like a reasonable way to handle this sorta thing. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMuS
On Sat, Apr 28, 2012 at 10:01:27AM +0200, m...@apollinemike.com wrote: On 28 avr. 2012, at 09:15, Graham Percival wrote: So... you *don't* want to set a precedent; you just want a quick answer about this specific case? I guess the general consensus is go ahead and we'll figure it out later. I *do* want this to work so well that it sets a solid precedent, If this is going to set a precedent, then I will say Do not submit LilyPond to LoMuS. I'm willing to go along with the current consensus only if there is the understanding that it does *not* set a precedent. I get the sense in a way that the precedent has already been set - if someone sees a cool opportunity (GSoC, LoMuS, whatever), email the list to call dibs if dibs must be called, make sure no one is opposed, apply, and do something fair with the money if money is to be gotten. In the GSoC case, Janek has $500 that he'll be donating to the organization in whatever way he sees fit. That is not what happened. Google is paying Janek $4500 directly. Carl is getting $500 for the project, which I guess he will spend how he sees fit. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
Graham Percival gra...@percival-music.ca writes: On Fri, Apr 27, 2012 at 11:14:23AM +0200, David Kastrup wrote: Graham Percival gra...@percival-music.ca writes: Then we'll have hard numbers on which developers are abusing the process. I mean, sure, we all know whose patches tend to be great and whose patches tend to be problematic... but a completely automated, objective approach would remove any personal bias. And those who generated more negative karma with their work than the average horse in the stables near our house will get banished from contributing for two weeks? No; I'm expecting the Hawthorne effect to take care of it. Get real. When the cure is worse than the symptom, leave it alone. Well, that would be the question. If programmers know that there will be a record of any bad patch submissions, would they be less likely to contribute? Or would they be more likely to check their work before submitting it? I'm obviously hoping for the latter, but I suppose that the former is still a logical possibility. It's small fry. The really bad things are those that are prodded until they pass the tests rather than the committer's level of understanding. And those would create positive Karma points. In fact, if you have to do half a dozen of iterations before getting things actually right on the somewhat more than superficial level provided by our tests, you'll have gained lots of good Karma on the road. We need more human feedback. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMuS
On 28 avr. 2012, at 10:13, Graham Percival wrote: On Sat, Apr 28, 2012 at 10:01:27AM +0200, m...@apollinemike.com wrote: On 28 avr. 2012, at 09:15, Graham Percival wrote: So... you *don't* want to set a precedent; you just want a quick answer about this specific case? I guess the general consensus is go ahead and we'll figure it out later. I *do* want this to work so well that it sets a solid precedent, If this is going to set a precedent, then I will say Do not submit LilyPond to LoMuS. I'm willing to go along with the current consensus only if there is the understanding that it does *not* set a precedent. What's wrong with the below being a precedent? It seems like a good idea that people have already rallied around in practice. I get the sense in a way that the precedent has already been set - if someone sees a cool opportunity (GSoC, LoMuS, whatever), email the list to call dibs if dibs must be called, make sure no one is opposed, apply, and do something fair with the money if money is to be gotten. In the GSoC case, Janek has $500 that he'll be donating to the organization in whatever way he sees fit. That is not what happened. Google is paying Janek $4500 directly. Carl is getting $500 for the project, which I guess he will spend how he sees fit. Irrespective of who gets the $500, it is the exact same principle as Lomus. Someone gets money meant for the organization and they can do with it as they see fit, which is what I'm suggesting above. It's actually a moot point w/ respect to precedent - I have a feeling that irrespective of what we call it (precedent, standard operating procedure, informal exchange of e-mails), what I suggest above is what will happen. The advantage of calling it a precedent is that we can write it up and put it in the CG so that newbs and first-time contributors feel empowered and encouraged to do this sorta thing instead of shying away because there's no history of it. However, I definitely don't want Lomus to get held up by the P word - I'm comfortable with saying that it is setting a simple Schmrecedent, where Schmrecedent is defined as something that is not a precedent but could eventually be. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
On Sat, Apr 28, 2012 at 10:13:50AM +0200, David Kastrup wrote: In fact, if you have to do half a dozen of iterations before getting things actually right on the somewhat more than superficial level provided by our tests, you'll have gained lots of good Karma on the road. I was thinking that each patch would generate its own karam, so each of those uploads that failed the tests would be -2 karma (or whatever the figure is), with only the final upload giving a +1. It's true that multiple rounds of patch, reviewer comment, patch, reviewer comment could potentially generate a karma windfall... but hey, since it's not like people can buy anything with karma, and as long as there's multiple rounds of not-automatic-failing patches, I'm fine with that. We need more human feedback. All my years of observing lilypond development suggests that saying we need xyz is a recipe for nothing happening. But hey, I'm not totally wedded to the idea of tracking karma, so meh. As long as I'm not personally playing nursemaid for people who don't run the basic tests, I don't mind if the patch-tester(s) want to keep on warning about flawed patches. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
Graham Percival gra...@percival-music.ca writes: On Sat, Apr 28, 2012 at 10:13:50AM +0200, David Kastrup wrote: In fact, if you have to do half a dozen of iterations before getting things actually right on the somewhat more than superficial level provided by our tests, you'll have gained lots of good Karma on the road. I was thinking that each patch would generate its own karam, so each of those uploads that failed the tests would be -2 karma (or whatever the figure is), with only the final upload giving a +1. The point was patches that did not fail the upload, because in spite of being horribly broken, they were massaged long enough to past the test suite. We need more human feedback. All my years of observing lilypond development suggests that saying we need xyz is a recipe for nothing happening. I prefer nothing happening over the wrong things happening. Call me conservative. But hey, I'm not totally wedded to the idea of tracking karma, so meh. As long as I'm not personally playing nursemaid for people who don't run the basic tests, I don't mind if the patch-tester(s) want to keep on warning about flawed patches. We have very little nursemaid material here, I am afraid. Do you really think that somebody who misses registering the responses on his issue report for whatever reason (which caused the last temper drop by me) will get phased by an arbitrary _number_ being displayed on the issue page, based on some accumulating metric? And will people be more motivated if they figure that their own Karma life savings are minuscule compared to Mike's daily fluctuations? -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: assistant release manger
- Original Message - From: Graham Percival gra...@percival-music.ca To: lilypond-devel@gnu.org Sent: Saturday, April 28, 2012 8:21 AM Subject: assistant release manger Given how things are going, it's past time that we have somebody else that can make releases. Who's interested in learning? Requirements: - powerful computer - can already compile GUB from scratch - is well known to lilypond developers (say, at least 1 year of lilypond development) - familiar with ssh, unix shell scripts, and python scripts If you are a candidate but feel that you are too busy working on other lilypond stuff, then findtrain a replacement for that stuff over the next few weeks so you can do releases. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel I guess I could do this. I would want to hand over bug duties - but Colin H is well-placed to take over as Meister and we would just need a volunteer for Sunday. I would want to schedule my work so that it could generally be done on a Sunday. James is the other obvious possibility, but I think he's already pretty busy. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: assistant release manger
Hello, On 28 April 2012 10:59, Phil Holmes m...@philholmes.net wrote: - Original Message - From: Graham Percival gra...@percival-music.ca To: lilypond-devel@gnu.org Sent: Saturday, April 28, 2012 8:21 AM Subject: assistant release manger Given how things are going, it's past time that we have somebody else that can make releases. Who's interested in learning? Requirements: - powerful computer Check. - can already compile GUB from scratch No. - is well known to lilypond developers (say, at least 1 year of lilypond development) Check. - familiar with ssh, unix shell scripts, and python scripts Define 'familiar', I can understand and can read all of the above (have done little personally with ssh but know what it is etc.) but I don't have the chops to write scripts or create/edit the 'routines' if needed. If you are a candidate but feel that you are too busy working on other lilypond stuff, then findtrain a replacement for that stuff over the next few weeks so you can do releases. - Graham I guess I could do this. I would want to hand over bug duties - but Colin H is well-placed to take over as Meister and we would just need a volunteer for Sunday. I would want to schedule my work so that it could generally be done on a Sunday. James is the other obvious possibility, but I think he's already pretty busy. It's not so much that, all these offers of 'university computers' could easily be set up to run patchy-merge-staging. Patchy-test while very important doesn't take too much of my LP time (I can run it in the background whenever I am at my computer), so that doesn't bother me doing that at all, it's more a case of LP doc work not getting done :) It's all fascinating stuff to me, so I don't mind poking with GUB but I am not sure if it is the best use of my time considering what I can do now (i.e. doc and bug squad) and what might drop if I moved to other work. Also are there other tasks (i.e. website building) that might be less of a learning curve for me (take extra work off of Graham) that might be better for me to start to tackle. Either way I don't mind what I end up doing - technical skill-set accepted. Being 'overwhelmed' isn't anything I ever worry about, there's always lots to do but only a finite amount of time to do it in. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Kicking off GSoC
Hi all, On Thu, Apr 26, 2012 at 4:24 PM, Janek Warchoł janek.lilyp...@gmail.com wrote: There's an unexpected problem: i caught some virus and i'm getting ill. It's too early to say whether i'll be able to do some serious work in the next week or i'll have to stay in bed, which is extremely unfortunate since i have a short holiday on my university and it would be perfect to use it for GSoC... :( I had quite high fever, however after taking some antipyretic i feel somewhat usable. I'll try now what i can do. cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 30 day webathon for kickstarter support (issue 6068045)
On Thu, Apr 26, 2012 at 8:07 AM, Graham Percival gra...@percival-music.ca wrote: I like the content of the announcement. I still don't like the idea of manually editing index.html. I was expecting/hoping for something like Documentation/web/twits.txt: - The Ensemble 101 is going on a European tour where they'll sing music typeset using LilyPond. Click a target=\_blank\ \href=\http://www.ensemble101.fr\;here/a to learn more! - The Birmingham Amateur Theatre is presenting Penzance Pirates, starring our documentation editor Trevor Daniels as the talking lion![1] - Project manager Graham Percival has successfully defended his PhD thesis. Only two days of edits left to go before he hands in the final version![2] - Valentin is trying soy milk with his cereal. Still on the fence about it.[3] - and then the javascript would parse that file. I'm not picky about the file format (it could be each line is a separate announcement; lines can be up to 256 chars long since that's probably easier to handle in javascript). +1 On Thu, Apr 26, 2012 at 9:54 AM, Trevor Daniels t.dani...@treda.co.uk wrote: Amazingly, there's an element of truth in it. Read Bicester for Birmingham, though. I'm nearing the end of typesetting a new vocal score for a musical pantomime based on Sullivan's music from the Savoy operas. It has 19 musical numbers, all with original words. It will be performed next November. Oh, and it has a talking dragon rather than a lion, but probably not played by me, although I have played Samuel twice in Pirates. lol! Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GSoC
David, Kieren, On Tue, Apr 24, 2012 at 10:16 PM, David Kastrup d...@gnu.org wrote: Nope. I had just sorted some of Kieren's wishes into categories that were reasonably easy to approach and ones that seemed harder, but I have not actually managed to start serious work (including thinking about suitable structures and algorithms) on any yet. ok. I'm looking forward to reading your reviews on my code when it's written! It might make sense for Kieren to send his wishlist as a whole to you, though: since you are prepared to delve decidedly deeper into the material as I a was, you'd likely arrive at different priorities and plans in connection with your own project that I did. Definitely! Kieren, please send me the examples you have - especially those that are connected to my Lyrics issues; maybe i've overlooked something or your thoughts will show me a new perspective. On Thu, Apr 26, 2012 at 5:38 PM, Kieren MacMillan kieren_macmil...@sympatico.ca wrote: i'd vote for having Extenders added by default, without the need to write them explicitly in ly code. Yes, but with an \autoExtendersOff option! :) sure! cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMuS
On Sat, Apr 28, 2012 at 10:13 AM, Graham Percival gra...@percival-music.ca wrote: On Sat, Apr 28, 2012 at 10:01:27AM +0200, m...@apollinemike.com wrote: On 28 avr. 2012, at 09:15, Graham Percival wrote: So... you *don't* want to set a precedent; you just want a quick answer about this specific case? I guess the general consensus is go ahead and we'll figure it out later. I *do* want this to work so well that it sets a solid precedent, If this is going to set a precedent, then I will say Do not submit LilyPond to LoMuS. I'm willing to go along with the current consensus only if there is the understanding that it does *not* set a precedent. I don't want to start a thorough discussion about our policies - these are just my ad-hoc feelings: - we don't touch anything that requires legal/formal bodies (GSoC was fine because it accepted individuals) - if someone does the work and wins some kind of contest/grant, the money is his and he can do with it anything he wants (for example pay some developer privately to handle some Lily issue). I get the sense in a way that the precedent has already been set - if someone sees a cool opportunity (GSoC, LoMuS, whatever), email the list to call dibs if dibs must be called, make sure no one is opposed, apply, and do something fair with the money if money is to be gotten. In the GSoC case, Janek has $500 that he'll be donating to the organization in whatever way he sees fit. That is not what happened. Google is paying Janek $4500 directly. Carl is getting $500 for the project, which I guess he will spend how he sees fit. Huh? I get $5000 (of which i'll spend quite a lot on Lily development, either directly or indirectly), and John Marchesi, GNU admin, gets $500 and gives it to whomever he decides - in our case most probably FSF. cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMuS
Janek Warchoł janek.lilyp...@gmail.com writes: Huh? I get $5000 (of which i'll spend quite a lot on Lily development, either directly or indirectly), and John Marchesi, GNU admin, gets $500 and gives it to whomever he decides - in our case most probably FSF. Depends on whether he gets a different request on behalf of the project's mentor if I understand correctly. Anyway, the principal point of the $5000 was not to spend it on Lily development. The point was to make it possible for you to focus on spending your _time_ on LilyPond. For the course of the project, and for giving you a jumpstart to stay on the project. The project will profit by a) the work you do, b) the difference in Janek skills at the end of the project, c) you not being burnt out financially and emotionally by having to juggle other responsibilities in addition to LilyPond just for survival and CV reasons. So don't think of spending the $5000 on LilyPond: spend your time. That's what this is supposed to enable. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMuS
On Sat, Apr 28, 2012 at 3:14 PM, David Kastrup d...@gnu.org wrote: Janek Warchoł janek.lilyp...@gmail.com writes: Huh? I get $5000 (of which i'll spend quite a lot on Lily development, either directly or indirectly), and John Marchesi, GNU admin, gets $500 and gives it to whomever he decides - in our case most probably FSF. Depends on whether he gets a different request on behalf of the project's mentor if I understand correctly. that's interesting, i haven't heard that we have some choice. Anyway, the principal point of the $5000 was not to spend it on Lily development. The point was to make it possible for you to focus on spending your _time_ on LilyPond. For the course of the project, and for giving you a jumpstart to stay on the project. The project will profit by a) the work you do, b) the difference in Janek skills at the end of the project, c) you not being burnt out financially and emotionally by having to juggle other responsibilities in addition to LilyPond just for survival and CV reasons. So don't think of spending the $5000 on LilyPond: spend your time. That's what this is supposed to enable. Of course. They give me money to enable me spending time on LilyPond instead of doing some other summertime job. The lucky thing is that my costs of living are currently quite low (since i'm living with parents, and outside of Euro zone). Thus, some/a lot of [1] money will remain - kind of a bonus. Since there are loads of things that i need in Lily, and i cannot code them all myself, i think i'll pay someone to do them :) cheers, Janek [1] depending on how much tax i'll have to pay ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMuS
Janek Warchoł janek.lilyp...@gmail.com writes: On Sat, Apr 28, 2012 at 3:14 PM, David Kastrup d...@gnu.org wrote: So don't think of spending the $5000 on LilyPond: spend your time. That's what this is supposed to enable. Of course. They give me money to enable me spending time on LilyPond instead of doing some other summertime job. The lucky thing is that my costs of living are currently quite low (since i'm living with parents, and outside of Euro zone). Thus, some/a lot of [1] money will remain - kind of a bonus. Trust me on that: it is not particularly likely that by the time you stop contributing to LilyPond, the total worth of the time and thinking you will have put into it will be less than that. Since there are loads of things that i need in Lily, and i cannot code them all myself, i think i'll pay someone to do them :) Won't likely work: I don't think there is much of a difference in helpfulness you can get with money from most LilyPond developers. They do what they can anyway. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: NR 1.2.3 Expl. manual accidentals + cadenzas (issue 5976056)
Reviewers: Graham Percival, Trevor Daniels,
Message:
Thanks Trevor, this one slipped past my radar.
http://codereview.appspot.com/5976056/diff/1/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
http://codereview.appspot.com/5976056/diff/1/Documentation/notation/rhythms.itely#newcode1415
Documentation/notation/rhythms.itely:1415: @cindex beams, unmetered
music
On 2012/04/01 22:09:16, Trevor Daniels wrote:
I think there should be index entries leading to this section starting
from both
bar line and bar number, as before. Why delete them?
It was an oversight inasmuch as I meant to put back bar line as I have
'bar numbers. Thanks for spotting.
I deleted the 'turning off' reference as that isn't what cadenza's do,
they force LP to 'ignore' them but not turn them off.
http://codereview.appspot.com/5976056/diff/1/Documentation/notation/rhythms.itely#newcode1422
Documentation/notation/rhythms.itely:1422: In metered music, measures
are calculated automatically for bar lines
On 2012/04/01 22:09:16, Trevor Daniels wrote:
I don't know what calculating measures means. Perhaps say, In
metered music
bar lines are inserted and bar numbers are calculated automatically.
Done.
http://codereview.appspot.com/5976056/diff/1/Documentation/notation/rhythms.itely#newcode1450
Documentation/notation/rhythms.itely:1450: Cadenzas are treated as a
@q{single measure} of music, even if one or
On 2012/04/01 22:09:16, Trevor Daniels wrote:
No, they can be shorter and within a measure of music. Perhaps say,
A new bar
is never started within a cadenza, even if one or more @code{\bar}
commands are
inserted within it.
Done.
http://codereview.appspot.com/5976056/diff/1/Documentation/notation/rhythms.itely#newcode1478
Documentation/notation/rhythms.itely:1478: These commands affect all
staves in the score, even when placed in just
On 2012/04/01 22:09:16, Trevor Daniels wrote:
We conventionally use the term predefined commands to refer to
commands
defined in ly/property-init.ly.
Of course! Thanks. Done.
http://codereview.appspot.com/5976056/diff/1/Documentation/notation/rhythms.itely#newcode1512
Documentation/notation/rhythms.itely:1512: In unmetered music, line and
page breaks will only occur at a bar line,
On 2012/04/01 22:09:16, Trevor Daniels wrote:
This is true generally, not just in unmetered music.
Automatic line and page breaks are inserted only at bar lines, so
@q{invisible}
bar lines will need to be inserted manually in long stretches of
unmetered music
to permit breaking:
Done.
Description:
Doc: NR 1.2.3 Expl. manual accidentals + cadenzas
Issue 2438
Added notes about using manual accidentals for reminder accidentals
when using \cadenzaOn.
Add it to note about manual beams.
Tidied up some 'third person' references and tightened up sentences
along with some 'long' @cindex entries.
Added an @ref{}
Please review this at http://codereview.appspot.com/5976056/
Affected files:
M Documentation/notation/rhythms.itely
Index: Documentation/notation/rhythms.itely
diff --git a/Documentation/notation/rhythms.itely
b/Documentation/notation/rhythms.itely
index
680e96c4fdeb78cc58dfb216915a8b60c463eab1..0052f78f23223f570dc2143367dceb568e8c8576
100644
--- a/Documentation/notation/rhythms.itely
+++ b/Documentation/notation/rhythms.itely
@@ -1401,21 +1401,31 @@ r8 e,8 | a4 c8 b[ c b] |
@node Unmetered music
@unnumberedsubsubsec Unmetered music
-@cindex bar lines, turning off
-@cindex bar numbering, turning off
@cindex cadenza
+@cindex cadenza, beams
+@cindex cadenza, accidentals
+@cindex cadenza, bar lines
+@cindex cadenza, bar numbers
@cindex unmetered music
+@cindex unmetered music, beams
+@cindex unmetered music, accidentals
+@cindex unmetered music, bar lines
+@cindex unmetered music, bar numbers
+@cindex accidentals, cadenzas
+@cindex accidentals, unmetered music
+@cindex beams, cadenzas
+@cindex beams, unmetered music
@funindex \cadenzaOn
@funindex cadenzaOn
@funindex \cadenzaOff
@funindex cadenzaOff
-Bar lines and bar numbers are calculated automatically. For
-unmetered music (some cadenzas, for example), this is not desirable.
-To turn off automatic calculation of bar lines and bar numbers,
-use the command @code{\cadenzaOn}, and use @code{\cadenzaOff}
-to turn them on again.
+In metered music bar lines are inserted and bar numbers are calculated
+automatically. In unmetered music (i.e. cadenzas), this is not
+desirable and can be @q{switched off} using the command
+@code{\cadenzaOn}, then @q{switched back on} at the appropriate place
+using @code{\cadenzaOff}.
@lilypond[verbatim,relative=2,quote]
c4 d e d
@@ -1426,8 +1436,7 @@ c4 c d8[ d d] f4 g4.
d4 e d c
@end lilypond
-Bar numbering is resumed at the end of the cadenza as if the
-cadenza were not there:
+Bar numbering is resumed at the end of the cadenza.
@lilypond[verbatim,relative=2,quote]
% Show all bar numbers
@@ -1440,29 +1449,37 @@ c4 c d8[ d d] f4 g4.
d4 e d c
@end
Re: lilypond bug 2368
Karol, I hope someone can help you do what you wish. It's definitely beyond my level of expertise. From my point of view on the bug squad, this doesn't look like something that needs to be handled by us, so I'm going to suggest that future correspondence on this issue not be sent to the bug squad. Thanks, Mark 2012/4/24 Karol Majewski karol.majew...@gmail.com Thank you Phil. Dear LilyPond friends: Janek, Phil, Colin, I have another big problem now. I'm trying to find a global setting that would allow to ignore collisions between ties and accidentals. For me, a tie-accidental collision looks a way better than a shifted tie - especially in tied chords in which one of the ties is unnaturaly shifted horizontaly. I'm almost sure that it is possible to achieve this, but I don't know how. Best wishes PS Janek, I saw that report. I really appreciate your contribution :) W dniu 13 kwietnia 2012 16:10 użytkownik Phil Holmes m...@philholmes.netnapisał: ** - Original Message - *From:* Karol Majewski karol.majew...@gmail.com *To:* Janek Warchoł janek.lilyp...@gmail.com *Cc:* LilyPond Developmet Team lilypond-devel@gnu.org ; Lilypond Bugs bug-lilyp...@gnu.org *Sent:* Wednesday, April 11, 2012 7:33 PM *Subject:* Re: lilypond bug 2368 OK, thanks for explanation! Actually, I've menaged to solve my problem by entering hidden notes with unHidden slur in separate voice. Now the tie refers to the right notes and appeals to my sense of aesthetic - despite colliding with an accidental (take a look at the attachment). Janek, I'm not a student of Politechnika Warszawska - neither former nor present. I'm a former student of Akademia Muzyczna w Gdańsku :) Best Wishes Karol Majewski Check my suggestion at http://code.google.com/p/lilypond/issues/detail?id=2368 - it works better and is designed for this. -- Phil Holmes ___ bug-lilypond mailing list bug-lilyp...@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
On 28 April 2012 10:30, Graham Percival gra...@percival-music.ca wrote: As long as I'm not personally playing nursemaid for people who don't run the basic tests It seems that the whole talk about running tests is only because of me not running them before uploading my first patches because I didn't know that I should do it. Do you have any other examples of committers that did not run tests? I guess that you don't have. Łukasz ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046)
Could you please change the mails' subject? :) I've started a thread: Lilypond patchy and other Lilypond problems for this discussion. Could you move there? Łukasz On 27 April 2012 19:43, Phil Holmes m...@philholmes.net wrote: - Original Message - From: James pkx1...@gmail.com To: Phil Holmes m...@philholmes.net Cc: m...@apollinemike.com; k-ohara5...@oco.net; d...@gnu.org; lilypond-devel@gnu.org Sent: Friday, April 27, 2012 5:58 PM Subject: Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046) You then need to tick a box more or two to enable that stuff in VBox or KVM. Remember though that LilyDev is 32bit so if you use KVM you must not go over 4096 for your RAM (even if you have more) else, I found, it will just default to 128mb! Vbox is a bit more smart, but you still cannot address more than 4GB of RAM in a 64bit VBox install using LilyDev. That said, I've never seen Lily builds take much RAM, so 4 GByte is normally plenty. -- Phil Holmes __**_ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/**listinfo/lilypond-develhttps://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
On 26 April 2012 20:41, Łukasz Czerwiński milimet...@gmail.com wrote: Mike, Graham and David wrote about more or less automatic running of tests and presenting only the results, possibly on an unused computer. I realised that I have a server on Dreamhost that probably could be such a computer - there is unlimited disk space and unlimited bandwidth (to some extend, I guess, but that will be enough for us). Now I'm trying to compile Lilypond on it - there are some libraries missing, I'm in progress of figuring out whether I can install it locally (it's a shared server, not a private one, so I don't have root on it). If yes and lilypond compiles, we could automatically pull git repo, run tests on it, pack the results and send an email with a link to them. There is Apache, PHP, MySQL there, so if you would like to do a website to present results directly on the server, it's possible :) I will finish installing Lilypond on a Dreamhost server soon, but because it's a shared server, I have some problems with overusing its resources. I've contacted Technical support and there are willing to help, e.g. giving me bigger limits or sth, BUT I must know one thing: How much CPU time and memory would regtests consume? How many times a day will they be run? Łukasz ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
Hello, On 28 April 2012 23:18, Łukasz Czerwiński milimet...@gmail.com wrote: On 28 April 2012 10:30, Graham Percival gra...@percival-music.ca wrote: As long as I'm not personally playing nursemaid for people who don't run the basic tests It seems that the whole talk about running tests is only because of me not running them before uploading my first patches because I didn't know that I should do it. Do you have any other examples of committers that did not run tests? I guess that you don't have. Oh yes there have been lots. I know because I used to apply patches and run the tests manually. The most common problems were devs 'forget' they have a 'dirty' branch and upload their patches based on their own branches not master. So the patch doesn't apply. http://code.google.com/p/lilypond/issues/detail?id=1953 (comment #1) This can cause hunk failures or make problems (where someone has changed a file but not added it to their commit). This doesn't mean they didn't run tests, necessarily, but it means they didn't run tests against current master. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
Hello, How much CPU time and memory would regtests consume? Depends on how many CPUs you can allocate. You can run reg tests on 1 CPU or xCPUs. You explicitly state the number in your make command 'make -j7 CPU_COUNT=7' test will use 7 CPUs 'make test' just uses 1 CPU (even if you have more than 1) 7 CPUs on my desktop are at about 90-100% for approximately 10 minutes for a reg test. RAM doesn't go much above 1.5GB. 1 CPU will be about 100% for 30 minutes (maybe more - depends on the speed of the CPU). Make doc takes a lot longer. How many times a day will they be run? You can run them as many times as you like. You need one reg test per patch-new tracker item. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
Łukasz Czerwiński milimet...@gmail.com writes: On 28 April 2012 10:30, Graham Percival gra...@percival-music.ca wrote: As long as I'm not personally playing nursemaid for people who don't run the basic tests It seems that the whole talk about running tests is only because of me not running them before uploading my first patches because I didn't know that I should do it. More like uploading patches with known problems. The notehead merging code would have given wrong results with pretty much every test merging noteheads. It's not like you missed out on running the regressions test suite: you did not apparently run any file relevant to the patch, and ignored the reviews repeatedly. Do you have any other examples of committers that did not run tests? I guess that you don't have. Plenty. Overall, the discipline has increased a lot in recent months, but partly because the procedures have been streamlined, partly because I was the one running the tests and tend to be somewhat less linear in my response than a karma point system. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
