Phil Holmes philholmes.net> writes:
> Anyway, I found a number that concern me. See them at
> http://www.philholmes.net/lilypond/regtestresults/2.17.1/.
I think all the concerns are covered by your tracker items, or otherwise
covered, or not concerns.
completion-heads-polyphony-2.png -- Mik
Great work so far.
Some minor suggestions:
http://codereview.appspot.com/6498052/diff/5001/scm/bar-line.scm
File scm/bar-line.scm (right):
http://codereview.appspot.com/6498052/diff/5001/scm/bar-line.scm#newcode203
scm/bar-line.scm:203:
If a user defines some curious bar-lines like:
#(define-
mike mikesolomon.org mikesolomon.org> writes:
> On 30 août 2012, at 00:44, David Kastrup gnu.org> wrote:
>
> > Much more worrying
> > in my opinion is that the staffs in the first third of the page are
> > crammed into each other so tightly that it becomes quite hard to guess
> > which of the
Hi David,
Il giorno mer, 29/08/2012 alle 16.37 +0200, David Kastrup ha scritto:
> Hi, I just looked at the repository, and picked out the patch that was
> required for bypassing the bashism. However, I don't think that the
> "touch all manual pages" thing actually belongs in there and should
> lik
On 30 août 2012, at 00:44, David Kastrup wrote:
> "m...@mikesolomon.org" writes:
>
>> The regtest that worries me most is les-nereides.ly.
>>
>> There is a comment starting on line 827 of axis-group-engraver.cc from
>> Joe (vintage 2008) that describes this scenario. It's just that excess
>>
"m...@mikesolomon.org" writes:
> The regtest that worries me most is les-nereides.ly.
>
> There is a comment starting on line 827 of axis-group-engraver.cc from
> Joe (vintage 2008) that describes this scenario. It's just that excess
> spacing has always hid it. It is now the time to tackle it h
Am 30.08.2012 00:07, schrieb David Kastrup:
Marc Hohl writes:
Am 29.08.2012 21:43, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-new Patch-needs_work
Comment #3 on issue 2790 by pkx1...@gmail.com: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues/det
2012/8/28 Mats Bengtsson :
> Han-Wen Nienhuys wrote:
>>>
>>> Change font license from GPL to dual licensed OFL / GPL (see
>>> http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=OFL_web)
>>
>> We have agreement of this from the people who were here:
>>
>> Author: Janek Warchol
>> Author: J
Marc Hohl writes:
> Am 29.08.2012 21:43, schrieb lilyp...@googlecode.com:
>> Updates:
>> Labels: -Patch-new Patch-needs_work
>>
>> Comment #3 on issue 2790 by pkx1...@gmail.com: Patch: bar-line
>> interface part 2/2
>> http://code.google.com/p/lilypond/issues/detail?id=2790#c3
>>
>> Patchy th
eluze writes:
> Phil Holmes wrote
>>
>> Can I just say that this is the first release I've build and uploaded?
>> Fingers crossed.
>>
>>
> congrats!
>
> however issue 2764 claims to solve the fingering problems of chords
> containing a second - I can not confirm this (picture attached)!
>
> h
Hello,
On 29 August 2012 13:26, Graham Percival wrote:
>
> Yes. If you're ok with this, let's continue using your computer
> as this. Could you re-enable the cronjob to run staging-merge
> every 6 hours?
OK I have set up all the push access and done a test and it seems to
work, I cannot yet
Hello,
On 29 August 2012 22:44, Marc Hohl wrote:
> Am 29.08.2012 21:43, schrieb lilyp...@googlecode.com:
>>
>> Updates:
>> Labels: -Patch-new Patch-needs_work
>>
>> Comment #3 on issue 2790 by pkx1...@gmail.com: Patch: bar-line interface
>> part 2/2
>> http://code.google.com/p/lilypond/issues
Am 29.08.2012 21:43, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-new Patch-needs_work
Comment #3 on issue 2790 by pkx1...@gmail.com: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues/detail?id=2790#c3
Patchy the autobot says: lots of: +programming er
I tried in on a score where should have its largest effect, a 41-page
score with 15 staves per system, and saw 8%.
user 2m26.191s -> 2m14.115s
sys0m1.097s-> 0m1.049s
http://codereview.appspot.com/6498053/
___
lilypond-devel m
On Wed, 29 Aug 2012 11:23:42 -0700, wrote:
http://codereview.appspot.com/6490043/diff/7001/lily/ledger-line-spanner.cc#newcode50
lily/ledger-line-spanner.cc:50: < Paper_column::get_rank
(previous_column)))
It seems that previous_column should have a rank falling before current column,
not after
Phil Holmes wrote
>
> Can I just say that this is the first release I've build and uploaded?
> Fingers crossed.
>
>
congrats!
however issue 2764 claims to solve the fingering problems of chords
containing a second - I can not confirm this (picture attached)!
http://lilypond.1069038.n5.nabble
Can I just say that this is the first release I've build and uploaded?
Fingers crossed.
--
Phil Holmes
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
- Original Message -
From:
To: "Phil Holmes"
Cc: "Devel"
Sent: Wednesday, August 29, 2012 7:34 PM
Subject: Re: 2.17.1 regtests
Thanks Phil!
The regtest that worries me most is les-nereides.ly.
There is a comment starting on line 827 of axis-group-engraver.cc from Joe
(vintage 2
On 29 août 2012, at 18:58, Phil Holmes wrote:
> I've just spent a happy few moments looking at around 900 regtest differences
> - most of the ones between 2.17.0 and 17.1. It's not a big deal except for
> my sanity - we did know there would be a lot. I've not checked them all,
> because my P
http://codereview.appspot.com/6472056/diff/1/lily/fingering-column.cc
File lily/fingering-column.cc (right):
http://codereview.appspot.com/6472056/diff/1/lily/fingering-column.cc#newcode38
lily/fingering-column.cc:38: map shifted;
It seems quite pointless to use a map here instead of a bool arra
http://codereview.appspot.com/6490043/diff/7001/lily/ledger-line-spanner.cc
File lily/ledger-line-spanner.cc (right):
http://codereview.appspot.com/6490043/diff/7001/lily/ledger-line-spanner.cc#newcode50
lily/ledger-line-spanner.cc:50: < Paper_column::get_rank
(previous_column)))
I'm having trou
LGTM
http://codereview.appspot.com/6498052/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
I've just spent a happy few moments looking at around 900 regtest
differences - most of the ones between 2.17.0 and 17.1. It's not a big deal
except for my sanity - we did know there would be a lot. I've not checked
them all, because my PC gets rather hot while running the tests and it went
s
On 2012/08/29 15:48:36, mike7 wrote:
On 29 août 2012, at 16:13, mailto:d...@gnu.org wrote:
>
http://codereview.appspot.com/6475065/diff/1/scm/define-grob-interfaces.scm#newcode223
> scm/define-grob-interfaces.scm:223: annotation."
> What about \clef "bass_8" or \clef "treble_15" ?
Should
On 29 août 2012, at 16:13, d...@gnu.org wrote:
>
> http://codereview.appspot.com/6475065/diff/1/scm/define-grob-interfaces.scm
> File scm/define-grob-interfaces.scm (right):
>
> http://codereview.appspot.com/6475065/diff/1/scm/define-grob-interfaces.scm#newcode223
> scm/define-grob-interfaces.s
On Wed, Aug 29, 2012 at 03:52:08PM +0200, Janek Warchoł wrote:
> i know that i'm late - forgot about it, sorry :( - but nevertheless it
> may still be possible:
> what about having a separate release containing only Mike's patch?
I think that's too much hassle right now with GUB changing so much
a
On Wed, Aug 29, 2012 at 03:17:40PM +0100, Phil Holmes wrote:
> git --git-dir downloads/lilypond/git push
> ssh+git://gperci...@git.sv.gnu.org/srv/git/lilypond.git/
> refs/tags/release/2.17.1-1:refs/tags/release/2.17.1-1
> Permission denied (publickey).
>
> I'm assuming that this is because GUB is
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Wednesday, August 29, 2012 3:39 PM
Subject: Re: Gub upload failure
"Phil Holmes" writes:
- Original Message -
From: "David Kastrup"
To:
Sent: Wednesday, August 29, 2012 3:21 PM
Subject: Re: Gub uplo
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To:
> Sent: Wednesday, August 29, 2012 3:21 PM
> Subject: Re: Gub upload failure
>
>
>> "Phil Holmes" writes:
>>
>>> OK - so it looks like I've now rsynched a few 100 MB of updates. I
>>> get this failure:
>>>
>>>
- Original Message -
From: "David Kastrup"
To:
Sent: Wednesday, August 29, 2012 3:21 PM
Subject: Re: Gub upload failure
"Phil Holmes" writes:
OK - so it looks like I've now rsynched a few 100 MB of updates. I
get this failure:
git --git-dir downloads/lilypond/git push
ssh+git://
"Phil Holmes" writes:
> OK - so it looks like I've now rsynched a few 100 MB of updates. I
> get this failure:
>
> git --git-dir downloads/lilypond/git push
> ssh+git://gperci...@git.sv.gnu.org/srv/git/lilypond.git/
> refs/tags/release/2.17.1-1:refs/tags/release/2.17.1-1
> Permission denied (pub
OK - so it looks like I've now rsynched a few 100 MB of updates. I get this
failure:
git --git-dir downloads/lilypond/git push
ssh+git://gperci...@git.sv.gnu.org/srv/git/lilypond.git/
refs/tags/release/2.17.1-1:refs/tags/release/2.17.1-1
Permission denied (publickey).
I'm assuming that this
http://codereview.appspot.com/6475065/diff/1/scm/define-grob-interfaces.scm
File scm/define-grob-interfaces.scm (right):
http://codereview.appspot.com/6475065/diff/1/scm/define-grob-interfaces.scm#newcode223
scm/define-grob-interfaces.scm:223: annotation."
What about \clef "bass_8" or \clef "tre
- Original Message -
From: "Janek Warchoł"
To: "Graham Percival"
Cc: "Phil Holmes" ; "Devel"
Sent: Wednesday, August 29, 2012 2:52 PM
Subject: Re: Regtests
On Wed, Aug 29, 2012 at 2:15 PM, Graham Percival
wrote:
On Wed, Aug 29, 2012 at 01:09:20PM +0100, Phil Holmes wrote:
2.17.1.
On Wed, Aug 29, 2012 at 2:15 PM, Graham Percival
wrote:
> On Wed, Aug 29, 2012 at 01:09:20PM +0100, Phil Holmes wrote:
>> 2.17.1. The official regtest comparison is against 2.15.38, because
>> of the vagaries of my initial GUB build.
>
> ouch, but not critical in this case. Mike's monster patch
2012/8/29 Francisco Vila :
> 2012/8/29 Phil Holmes :
>>> We say just "using the Span_stem_engraver" but the user can be
>>> confused when adding/removing other engravers because it is sometimes
>>> #Name_engraver and sometimes "Name_engraver".
>> I don't believe that would be the right place to ch
Janek Warchoł writes:
> On Wed, Aug 29, 2012 at 3:15 PM, David Kastrup wrote:
>> Graham Percival writes:
>>
>>> At the Waltrop meeting, Janek proposed a number of interesting but
>>> potentially disruptive changes to the lilypond syntax. On a
>>> personal note, I really like most of them, but
On Wed, Aug 29, 2012 at 2:29 PM, David Kastrup wrote:
> Maybe Ian could push his current branch to some dev/* branch so that one
> can make a rough estimate what the costs of various ways of integration
> would turn out to be? fixscm.sh is basically an esthetic fix. We
> should do it when we are
Il giorno mer, 29/08/2012 alle 14.28 +0100, James ha scritto:
> They did reduce significantly since Phil and I were able to run tests
> quickly. I often would run tests myself after the normal patchy tests
> simply because I knew a change was significant (like Mike's skyline
> for instance or Phils
On Wed, Aug 29, 2012 at 3:15 PM, David Kastrup wrote:
> Graham Percival writes:
>
>> At the Waltrop meeting, Janek proposed a number of interesting but
>> potentially disruptive changes to the lilypond syntax. On a
>> personal note, I really like most of them, but it will take a good
>> chunk of
On Wed, Aug 29, 2012 at 03:15:08PM +0200, David Kastrup wrote:
> Graham Percival writes:
>
> > Thoughts? opinions? alternatives that I haven't considered?
> > These discussions are going to produce a *lot* of emails.
>
> And if they come to conclusions, they are going to produce effects on
> e
Hello
On 29 August 2012 14:19, Graham Percival wrote:
> On Wed, Aug 29, 2012 at 02:09:43PM +0100, James wrote:
>> Just an off-the-cuff suggestion. If we had a 'patch-new-doc' and a
>> 'patch-new' label would that be useful and tell patchy if it sees the
>> former to build doc as well?
>
> I suppo
Il giorno mer, 29/08/2012 alle 14.09 +0100, James ha scritto:
> Just an off-the-cuff suggestion. If we had a 'patch-new-doc' and a
> 'patch-new' label would that be useful and tell patchy if it sees the
> former to build doc as well?
This is a possible option. Another that I prefer is letting Pat
On Wed, Aug 29, 2012 at 02:09:43PM +0100, James wrote:
> Just an off-the-cuff suggestion. If we had a 'patch-new-doc' and a
> 'patch-new' label would that be useful and tell patchy if it sees the
> former to build doc as well?
I suppose so, although people uploading with git-cl would need to
speci
Graham Percival writes:
> At the Waltrop meeting, Janek proposed a number of interesting but
> potentially disruptive changes to the lilypond syntax. On a
> personal note, I really like most of them, but it will take a good
> chunk of work before they're ready to discuss on the main
> developmen
On Wed, Aug 29, 2012 at 2:10 PM, Graham Percival
wrote:
> At the Waltrop meeting, Janek proposed a number of interesting but
> potentially disruptive changes to the lilypond syntax. On a
> personal note, I really like most of them, [...]
I'm very happy to hear this :)
> I'm not enthusiastic abo
Hello,
On 29 August 2012 14:03, John Mandereau wrote:
> Hi Graham , James and LilyPond folks,
> Il giorno mer, 29/08/2012 alle 13.26 +0100, Graham Percival ha scritto:
>> John, could you disable staging-merge on Grenouille? that should
>> free up some computing resources for the other tasks.
>
>
Hi Graham , James and LilyPond folks,
Il giorno mer, 29/08/2012 alle 13.26 +0100, Graham Percival ha scritto:
> John, could you disable staging-merge on Grenouille? that should
> free up some computing resources for the other tasks.
Done, I also just reenabled patches tests, which given the new s
Hello,
On 29 August 2012 13:26, Graham Percival wrote:
> On Tue, Aug 28, 2012 at 10:44:17AM +0100, James wrote:
>> On 28 August 2012 08:17, Graham Percival wrote:
>> > - Patchy staging-merge: powerful computer, no fixed internet
>> > connection. Every 6 hours?
>>
>> As you know you have mine
Graham Percival writes:
> As per GOP 2-4 - C++ and scheme indentation, we now have a
> fixscm.sh in the source tree. Running this was postponed pending
> Mike's monster skyline patch and possibly some sort of guile 2.0
> thing.
>
> What's the status of the guile 2.0 patch? In particular, is it
On Tue, Aug 28, 2012 at 10:44:17AM +0100, James wrote:
> On 28 August 2012 08:17, Graham Percival wrote:
> > - Patchy staging-merge: powerful computer, no fixed internet
> > connection. Every 6 hours?
>
> As you know you have mine that already does test-patchy (manually) and
> has done 'stagin
Il 29/08/2012 14:21, Graham Percival ha scritto:
On Tue, Aug 28, 2012 at 07:11:10PM +0200, Federico Bruni wrote:
I can launch 'make website' now, but the css stylesheet is not loaded.
Because there's no css/ directory in out-website/
Yes, because
out-website/index.html
is not the real websi
On Tue, Aug 28, 2012 at 07:11:10PM +0200, Federico Bruni wrote:
> I can launch 'make website' now, but the css stylesheet is not loaded.
> Because there's no css/ directory in out-website/
Yes, because
out-website/index.html
is not the real website. Intead, look at
out-website/website/index.h
On Wed, Aug 29, 2012 at 01:09:20PM +0100, Phil Holmes wrote:
> 2.17.1. The official regtest comparison is against 2.15.38, because
> of the vagaries of my initial GUB build.
ouch, but not critical in this case. Mike's monster patch changes
pretty much everything, so a regtest comparison isn't us
At the Waltrop meeting, Janek proposed a number of interesting but
potentially disruptive changes to the lilypond syntax. On a
personal note, I really like most of them, but it will take a good
chunk of work before they're ready to discuss on the main
development list.
Further complicating issues
2.16.0 versus 2.15.95. Tiny differences in the dots on volta repeat
numbers. Nothing else. If anyone wants to see examples, please let me
know.
2.17.0 versus 2.16.0. Two major differences which aren't picked up by the
general regtest checker. 1) Fret diagrams - the line showing top of the
On Tue, Aug 28, 2012 at 11:18 PM, Graham Percival
wrote:
> (don't see this as me withdrawing from the project; I am now
> going to seriously whip the CG into shape and mentor new
> contributors. I'll talk more about that in a separate email)
Cool! That definitely sounds like +1 for Graham
After further investiation of astyle at the Waltrop meeting, I've
tweaked GOP2-4 - C++ and scheme indentation.
Instead of using astyle 2.02 strictly, we will also allow astyle
2.02.1. The later version changes:
* bar;
into
*bar;
which matches the way that we format pointers which do not have
As per GOP 2-4 - C++ and scheme indentation, we now have a
fixscm.sh in the source tree. Running this was postponed pending
Mike's monster skyline patch and possibly some sort of guile 2.0
thing.
What's the status of the guile 2.0 patch? In particular, is it
safe to run fixscm.sh now, or should
http://codereview.appspot.com/6474066/diff/5001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6474066/diff/5001/Documentation/notation/input.itely#newcode368
Documentation/notation/input.itely:368: A @code{\header} block. This
On Wed, Aug 29, 2012 at 11:58:12AM +0200, David Kastrup wrote:
> "Phil Holmes" writes:
> > Well, actually, I omitted that part of the instruction, since I could
> > see my user in group lilypond...
>
> Your running processes don't change membership. Use
> id
> to see what the actual memberships
Graham Percival writes:
> On Wed, Aug 29, 2012 at 10:16:18AM +0100, Phil Holmes wrote:
>> For reference, I added the new group and added my gub user to that
>> group, and the script still barfed. It can't change the properties
>> of the files unless it has the permissions to do that, which it
>>
"Phil Holmes" writes:
> - Original Message -
> From: "Graham Percival"
> To: "Phil Holmes"
> Cc: "Devel"
> Sent: Wednesday, August 29, 2012 10:25 AM
> Subject: Re: GUB upload error
>
>
>> On Wed, Aug 29, 2012 at 10:16:18AM +0100, Phil Holmes wrote:
>>> For reference, I added the new g
http://codereview.appspot.com/6474066/diff/5001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6474066/diff/5001/Documentation/notation/input.itely#newcode368
Documentation/notation/input.itely:368: A @code{\header} block. This
LGTM, can be pushed directly to staging.
http://codereview.appspot.com/6479058/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
http://codereview.appspot.com/6492045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM, can be pushed directly to staging.
http://codereview.appspot.com/6489047/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello list,
I just uploaded part 2/2 of the "Great Bar Line Interface Project",
see
http://codereview.appspot.com/6498052
I hope that it is understandable what I have done, but since the
description of the patch is rather short, I'll give an overview:
* the input string of a bar line called by
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc: "Devel"
Sent: Wednesday, August 29, 2012 10:25 AM
Subject: Re: GUB upload error
On Wed, Aug 29, 2012 at 10:16:18AM +0100, Phil Holmes wrote:
For reference, I added the new group and added my gub user to that
group,
On Wed, Aug 29, 2012 at 10:16:18AM +0100, Phil Holmes wrote:
> For reference, I added the new group and added my gub user to that
> group, and the script still barfed. It can't change the properties
> of the files unless it has the permissions to do that, which it
> doesn't.
Hmm, are you sure you
Am 29.08.2012 00:14, schrieb Trevor Daniels:
Marc Hohl wrote Tuesday, August 28, 2012 9:56 PM
Am 28.08.2012 22:52, schrieb Graham Percival:
On Tue, Aug 28, 2012 at 10:45:00PM +0200, Marc Hohl wrote:
Am 28.08.2012 20:52, schrieb David Kastrup:
Marc Hohl writes:
After searching a bit more,
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc: "Devel"
Sent: Tuesday, August 28, 2012 7:15 PM
Subject: Re: GUB upload error
On Tue, Aug 28, 2012 at 03:43:40PM +0100, Phil Holmes wrote:
gub@gub-virtualbox:~/gub$ make lilypond-upload
LILYPOND_BRANCH=release/unstab
David Kastrup writes:
> "m...@mikesolomon.org" writes:
>
>> Hey all,
>>
>> Could someone well-versed in guile try running primitive-load-path on
>> the attached file with and without the last line commented. Without
>> the last line commented, on my machine, I get:
>>
>> guile> (primitive-load-p
"m...@mikesolomon.org" writes:
> Hey all,
>
> Could someone well-versed in guile try running primitive-load-path on
> the attached file with and without the last line commented. Without
> the last line commented, on my machine, I get:
>
> guile> (primitive-load-path "/home/mikesol/pleasework.lyau
"Trevor Daniels" writes:
>> Note the project lead being on the high horse after having wrapped up
>> the 2.17.0 release for good.
>
> Thanks for the photo. Not as good as being there, but really nice to see.
>
> I know Graham and I think I can recognise you, David, but it would
> be good to be a
Hey all,
Could someone well-versed in guile try running primitive-load-path on the
attached file with and without the last line commented. Without the last line
commented, on my machine, I get:
guile> (primitive-load-path "/home/mikesol/pleasework.lyaux")
Backtrace:
In standard input:
1: 0*
76 matches
Mail list logo
