Re: possible tuplet bug?

[David Kastrup]

David Nalesnik <address@hidden> writes:

> In the "patch" below, I've suggested a modification of the relevant
> function in tuplet-bracket.cc which appears to fix the problem.  (The
> replacement is above the commented-out section of the original.) You can
> see the results in the second image.
>
>
> I hesitate to submit a formal patch because I haven't worked with C++ in
> LilyPond before,

Formal or not, trying to figure out what you changed from just a quote
of code is a major nuisance and unreliable.

So even if you don't want to propose a "formal" commit, using "git diff"
in order to produce a properly readable patch that you can attach to a
mail will make people's life easier.

-- 
David Kastrup