lilypond-devel
[Top][All Lists]

## Re: Snippets in doc compile different from stand-alone

 From: Carl Sorensen Subject: Re: Snippets in doc compile different from stand-alone Date: Fri, 10 Jul 2009 17:06:19 -0600

```

On 7/10/09 4:58 PM, "John Mandereau" <address@hidden> wrote:

>> Ahh -- there is a clue here that I hadn't noticed before.  The comments in
>> the code are different in the snippet from  rhythms.itely and the doc
>> output.
>>
>> That means that the snippet in rhythms.itely is *not* the one that is being
>> compiled for the docs.
>
> What are the exact differences?

The difference is two lines of comments.  The one that is showing up in the
docs is an older version than the one that is currently in rhythms.itely.

Please note that the snippet is not an included file, but is actually part
of the text in rhythms.itely.  It's as if the snippet database is somehow
not being updated.

I'm not sure how to best show you the exact differences.  Let me do my best.

Here is what shows up in the docs:

\time 7/8
% rhythm 3-1-1-2
% Context not specified - does not work correctly
\overrideBeamSettings #'Voice #'(7 . 8) #'end #'((* . (3 1 1 2)))
<< {a8 a a a16 a a a a8 a} \\ {f4. f8 f f f} >>

% Works correctly with context specified
\overrideBeamSettings #'Staff #'(7 . 8) #'end #'((* . (3 1 1 2)))
<< {a8 a a a16 a a a a8 a} \\ {f4. f8 f f f} >>

Here is what is in rhythms.itely

@lilypond[quote,verbatim,relative=2]
\time 7/8
% rhythm 3-1-1-2
% Context not specified - does not work correctly
% Because of autogenerated voices, all beating will
% be at beatLength (1 . 8)
\overrideBeamSettings #'Voice #'(7 . 8) #'end #'((* . (3 1 1 2)))
<< {a8 a a a16 a a a a8 a} \\ {f4. f8 f f f} >>

% Works correctly with context specified
\overrideBeamSettings #'Staff #'(7 . 8) #'end #'((* . (3 1 1 2)))
<< {a8 a a a16 a a a a8 a} \\ {f4. f8 f f f} >>
@end lilypond

When I copy either snippet to a .ly file and surround it with
\relative c''{}, it compiles correctly.

But in the docs, it does not.  I suspect it's actually not compiling at all,
but just being included from the database somehow.  And the LilyPond output
is from a buggy previous version that I was working on.  But I don't know
how to track that down.