On Mon, Jan 10, 2011 at 12:29:23PM -0800, Keith OHara wrote:
> In addition to showing images of desired behavior, people sometimes describe
> it in text. Werner and some others report bugs in the form of a statement of
> desired behavior and then a tiny example to show what they don't like. The
> tiny example tells us the precise subject; the text tells us the point.
>
> You might want to use this kind of report in step 2: create a bug report.
Good idea.
> % I expected the two halves of a tie to curve in
> % the same direction, either both up or both down,
> % when the tie is broken at the end of a line.
> %
> % Sometimes [ed: in the past, but no longer]
> % LilyPond engraves them with opposite directions
>
> \version "2.10.1"
>
> \relative c'' {
> \time 4/4 bes1 ~ \break
> \time 3/4 bes2.
> }
To be clear, you're suggesting that we remove the octavation
example and use this instead?
I'm not entirely sold on this particular example -- it doesn't
follow our input syntax style, and if we add all the linebreaks
that would be required, it gets a bit long. Can you (or anybody
else) create a different example, or modify the existing one?
ETA: 15 minutes, including all discussion. Yes, I seriously think
it's worth nitpicking and editing that much for this example.
Cheers,
- Graham
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
