Doc: Remove fragment option from @lilypond LM

Doc: Remove fragment option from @lilypond LM

[Trevor Daniels, 2010-12-01 16:53:06]

Looks OK, but you might as well remove ragged-right while you're updating these
lines.  It's no longer necessary for most of these examples, those that fit on
one line.

Trevor

http://codereview.appspot.com/3369041/diff/1/Documentation/learning/fundament...
File Documentation/learning/fundamental.itely (right):

http://codereview.appspot.com/3369041/diff/1/Documentation/learning/fundament...
Documentation/learning/fundamental.itely:534:
@lilypond[quote,verbatim,ragged-right]
Should also have relative=2

[Graham Percival (old account), 2010-12-02 09:12:00]

I'm not totally sold on the first two things.

Trevor: I agree that [ragged-right] should be removed eventually, but let's
leave that for a later patch.

http://codereview.appspot.com/3369041/diff/1/Documentation/learning/fundament...
File Documentation/learning/fundamental.itely (right):

http://codereview.appspot.com/3369041/diff/1/Documentation/learning/fundament...
Documentation/learning/fundamental.itely:524: { g8\( a b[ c b\) a] g4 }
the {} around the entire input looks like a mistake (in the original version as
well; it's not your fault, James!), but see my next comment.

http://codereview.appspot.com/3369041/diff/1/Documentation/learning/fundament...
Documentation/learning/fundamental.itely:534:
@lilypond[quote,verbatim,ragged-right]
On 2010/12/01 16:53:06, Trevor Daniels wrote:
> Should also have relative=2

I see an inconsistency between having [relative=2] and having the actual input
surrounded with
{
  ...
}

Unless you're doing something fancy here (such as showing the exact text that
you're going to "copy and paste" into a larger example later on), then the {}
should be removed.

[Jlowe, 2010-12-02 18:00:11]

>
http://codereview.appspot.com/3369041/diff/1/Documentation/learning/fundament...
> Documentation/learning/fundamental.itely:534:
> @lilypond[quote,verbatim,ragged-right]
> On 2010/12/01 16:53:06, Trevor Daniels wrote:
> > Should also have relative=2
> 
> I see an inconsistency between having [relative=2] and having the actual input
> surrounded with
> {
>   ...
> }
> 
> Unless you're doing something fancy here (such as showing the exact text that
> you're going to "copy and paste" into a larger example later on), then the {}
> should be removed.

Removing the {} but adding the relative caused the note pitches to change
dramatically. so I had to make additional changes to the pitch indicators in the
example to bring it back inline with the original example.

[Trevor Daniels, 2010-12-03 00:10:31]

On 2010/12/02 18:00:11, Jlowe wrote:

> Removing the {} but adding the relative caused the note 
> pitches to change dramatically. so I had to make additional 
> changes to the pitch indicators in the example to bring it 
> back inline with the original example.

That's fine.  It's more in keeping with the style of the rest 
of the documentation now, which rarely uses absolute pitches.

[Graham Percival (old account), 2010-12-07 17:28:53]

LGTM

[Graham Percival (old account), 2010-12-14 15:42:08]

This was pushed; could you close this issue?