On Thu, May 20, 2010 at 12:23 AM, Kieren MacMillan
wrote:
> Ok, but I have identified at least three bounties (of my own) that
> weren't/aren't tagged or tracked... so clearly it is already too much work,
> right?
Please give the bug squad a ping when this happens. Even though our
response-time
hi Neil,
>> updated the patch fixing the issue and attached
>> an example where the previous version failed.
>
> LGTM.
>
> A few minor nitpicks:
>
> + /*
> + note that note_dur may be strictly less than left_to_do_
> + (say, if left_to_do_ == 5/8)
> + */
>
> This comment woul
On 5/20/10 1:45 AM, "Benkő Pál" wrote:
>
>> Please change this to something which explains that the polyphony in
>> this test works properly.
>
> what about "Versions up to 2.13.21 got complex completion heads wrong
> in polyphonic environment"?
A better phrase would be:
"Complex completion h
Hello. This patch includes a fix for remove_unneeded_anchor:
therefore, the other patch which also fixed it should NOT be applied.
The patch has a side effect of eliminating the side menu highlighting
of the current section. I have not investigated this new problem yet.
If anyone has a clever idea
Carl Sorensen wrote:
On 5/19/10 3:41 PM, "Neil Puttock" wrote:
On 19 May 2010 10:59, Mark Polesky wrote:
Right, so if \partial generates odd warnings or effects,
then measurePosition would too. Why would measurePosition
behave any differently, as the text suggests?
\part
On Thu, May 20, 2010 at 1:06 PM, Francisco Vila wrote:
> Hello. This patch includes a fix for remove_unneeded_anchor:
> therefore, the other patch which also fixed it should NOT be applied.
Thanks, looks great! I am **so** happy to get rid of those
meaningless #foo portions of urls.
> The patc
At the very top right of
http://lilypond.org/doc/v2.13/Documentation/notation/spanners
The "next" link for "Using the spanner-interface" is broken.
I assume there are other cases, too?
- Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.
2010/5/20 Mark Polesky :
> At the very top right of
> http://lilypond.org/doc/v2.13/Documentation/notation/spanners
>
> The "next" link for "Using the spanner-interface" is broken.
> I assume there are other cases, too?
I think this is caused by lack of @menu in the Spanners subsection of
notation
