I think I like the approach.
Right now, we can
\score {
\music
\layout{} }
\score {
\unfoldRepeats \music
\midi{} }
And if I understand, when this is finished we can
\score {
\music
\layout{}
\midi{midiUnfoldRepeats = #'(percent-repeated-music) } }
I did not before realize that the music
On 2013/12/21 02:58:05, Devon Schudy wrote:
OK: Issue 3744 fixes that for all score-level translators by creating
the Score context before iteration starts. Creating it later was
dubious anyway, because Score_engraver or Score_performer is needed
for iteration to work. AFAICT it's never valid to
You want to change the text as well as the example.
Giving four staves lets a user see more clearly what happens if he
removes \accepts.
https://codereview.appspot.com/44420043/diff/1/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (right):
ht
d...@gnu.org wrote:
> Ok, here is a filthy bad thing: in issue 2392 I finally punted and gave
> up on start_translation_timestep in implicitly created contexts to be
> reliably run.
>
> That means that for implicitly created contexts from a
> Simple_music_iterator, start_translation_timestep will
-- Forwarded message --
From:
Date: Thu, Dec 19, 2013 at 5:33 AM
Subject: Re: Issue 3714 in lilypond: website: use colors to
distinguish each manual and stable vs. development
To: carlopeter...@gmail.com
Updates:
Labels: -Patch-countdown Patch-push
Comment #15 on issue
On 20/12/13 12:29, David Kastrup wrote:
James writes:
Hello,
On 20/12/13 11:35, David Kastrup wrote:
We'll try running 2.18.0 out on December 28. There are several things
that need doing till then: Documentation/included/authors.itexi needs to
get updated.
I've done that in the past, so I'
https://codereview.appspot.com/42600043/diff/20001/lily/audio-item.cc
File lily/audio-item.cc (right):
https://codereview.appspot.com/42600043/diff/20001/lily/audio-item.cc#newcode44
lily/audio-item.cc:44: return int (moment_to_ticks (when_));
Why cast to int here? moment_to_ticks is already an
- Original Message -
From: "James"
To: "Phil Holmes" ; "Developers List"
Sent: Friday, December 20, 2013 12:29 PM
Subject: Re: Question about Snippets new vs LSR
On 20/12/13 10:45, Phil Holmes wrote:
- Original Message - From: "Pkx"
To: "Developers List"
So I have a trac
On 20/12/13 10:45, Phil Holmes wrote:
- Original Message - From: "Pkx"
To: "Developers List"
So I have a tracker issue that recommends changing a snippet that
comes from the LSR but with a syntax that won't work with the current
version of LP in the LSR (which I think is 2.14.somethi
James writes:
> Hello,
>
> On 20/12/13 11:35, David Kastrup wrote:
>> We'll try running 2.18.0 out on December 28. There are several things
>> that need doing till then: Documentation/included/authors.itexi needs to
>> get updated.
> I've done that in the past, so I'll go through that this eveni
Hello,
On 20/12/13 11:35, David Kastrup wrote:
We'll try running 2.18.0 out on December 28. There are several things
that need doing till then: Documentation/included/authors.itexi needs to
get updated.
I've done that in the past, so I'll go through that this evening or
tomorrow evening and ge
We'll try running 2.18.0 out on December 28. There are several things
that need doing till then: Documentation/included/authors.itexi needs to
get updated.
git shortlog -s origin/stable/2.16..origin/stable/2.18
should give the current list of committers (38 is more than I expected,
actually
We'll try running 2.18.0 out on December 28. There are several things
that need doing till then: Documentation/included/authors.itexi needs to
get updated.
git shortlog -s origin/stable/2.16..origin/stable/2.18
should give the current list of committers (38 is more than I expected,
actually
- Original Message -
From: "Pkx"
To: "Developers List"
So I have a tracker issue that recommends changing a snippet that comes
from the LSR but with a syntax that won't work with the current version of
LP in the LSR (which I think is 2.14.something right?).
So in that case if I cre
Am 20.12.2013 11:25, schrieb David Kastrup:
Would you suggest to put such a series in a separate "thread" (by a
>merge no-ff) or not.
Usually not. But some of that might be pulled into a single commit.
>
OK, thanks.
Urs
___
lilypond-devel mailin
Urs Liska writes:
> Am 20.12.2013 11:12, schrieb David Kastrup:
>> As the typical victims for pushers are often able to grant push access,
>> you'll probably not have to go through this very often before they beg
>> you to accept push access.
>
> I think I will do that soon.
> Some time in the pa
Am 20.12.2013 11:12, schrieb David Kastrup:
As the typical victims for pushers are often able to grant push access,
you'll probably not have to go through this very often before they beg
you to accept push access.
I think I will do that soon.
Some time in the past I would have considered it a
Urs Liska writes:
> Am 20.12.2013 10:45, schrieb Trevor Daniels:
>>> 3)
>>> >What to do if my branch contains more than one commit?
>>> >Should I squash them so the patch is one (big) commit? I wouldn't like
>>> >that, for example because I would separate commits that move stuff (e.g.
>>> >to oth
Thanks for the explanations.
Basically everything is like I would have expected, but I think I will
try to add some explanations to CG when I've time.
Urs
Am 20.12.2013 11:00, schrieb David Kastrup:
Urs Liska writes:
Am 19.12.2013 11:32, schrieb lilyp...@googlecode.com:
Updates:
La
Urs Liska wrote Friday, December 20, 2013 9:48 AM
> Am 20.12.2013 10:45, schrieb Trevor Daniels:
>>> 3)
>>> >What to do if my branch contains more than one commit?
>>> >Should I squash them so the patch is one (big) commit? I wouldn't like
>>> >that, for example because I would separate commits
Urs Liska writes:
> Am 19.12.2013 11:32, schrieb lilyp...@googlecode.com:
>> Updates:
>> Labels: -Patch-countdown Patch-push
>>
>> Comment #4 on issue 3718 by pkx166h: Patch: Web: Reword contactUsAbout
>> macro
>> http://code.google.com/p/lilypond/issues/detail?id=3718
>>
>> Patch counted do
Am 20.12.2013 10:45, schrieb Trevor Daniels:
Am 19.12.2013 11:32, schrieblilyp...@googlecode.com:
>>Patch counted down - please push
>
>What should I do now?
>The CG says I should "send the patch to my mentor", but obviously this
>isn't applicable.
Create a git format patch, post it on -dev an
Am 20.12.2013 10:45, schrieb Trevor Daniels:
3)
>What to do if my branch contains more than one commit?
>Should I squash them so the patch is one (big) commit? I wouldn't like
>that, for example because I would separate commits that move stuff (e.g.
>to other website nodes) from commits that chan
Urs Liska wrote Friday, December 20, 2013 9:28 AM
> Am 19.12.2013 11:32, schrieb lilyp...@googlecode.com:
>> Patch counted down - please push
>
> What should I do now?
> The CG says I should "send the patch to my mentor", but obviously this
> isn't applicable.
Create a git format patch, post
Am 19.12.2013 11:32, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-countdown Patch-push
Comment #4 on issue 3718 by pkx166h: Patch: Web: Reword contactUsAbout
macro
http://code.google.com/p/lilypond/issues/detail?id=3718
Patch counted down - please push
What should I do now?
https://codereview.appspot.com/42770043/diff/1/Documentation/web/introduction.itexi
File Documentation/web/introduction.itexi (right):
https://codereview.appspot.com/42770043/diff/1/Documentation/web/introduction.itexi#newcode119
Documentation/web/introduction.itexi:119: @divClass{color2}
On 201
Hello,
regarding editing/creating snippets says in the CG:
http://lilypond.org/doc/v2.17/Documentation/contributor-big-page#adding-and-editing-snippets
Fixing Snippets in LilyPond Sources
--snip--
If the snippet comes from the LSR, also apply the fix to the snippet in
the LSR and send a notif
27 matches
Mail list logo
