RE: Clarification for \null in \header markups

[James Lowe]

Mark,

)-----Original Message-----
)From: Mark Polesky [mailto:address@hidden
)Sent: 01 April 2011 07:04
)To: 'address@hidden'; James Lowe
)Subject: Re: Clarification for \null in \header markups
)
)James Lowe wrote:
)> I am making a patch for some updates for Titles and Headers and a para
)> in the doc currently says:
)>
)> "Text fields left unset in a \header block are replaced with \null
)> markups so space is not wasted...."
)>
)> Then there is an @c from Mark Polesky asking if this is true?
)>
)> I wondered if anyone knew or if it even matters that we state this or
)> not.
)
)
)James,
)
)Yikes, my last post was 100 days ago!  Anyway, I'm just writing to clarify for
)everyone else, you must be referring to this unpublished patch of mine
)from December:
)http://codereview.appspot.com/3667041
)The text and @c you mention do not appear in the savannah repo.
)
)I'm chiming in here mostly because I put a lot of work into that patch, and
)the consensus was that the content was good but the format wasn't quite
)right.  I subsequently got too busy to fix it, but there are some good parts
)there that (I
)think) should clear up some confusing things for a lot of users.
)
)So if someone (you or anyone else) has time and interest, it would be
)*really* nice to see the useful bits incorporated (maybe with a little
)attribution in the commit comments), presumably in a better format.
)

Don't worry, I've been on it, I didn't want to see this work go to waste as the 
patch became stale. So I've edited your work and created a new patch

http://codereview.appspot.com/4124056/

and this is the latest iteration of your patch.

Although it's taking me a while as we have been 'playing' about with getting a 
decent papersize to show the effects that control things over multiple pages 
without having to print huge a4 examples on the page and without having to put 
in the explicit paper size in the @lilypond code. Graham did some tweaks so 
that you can put a paper size in the @lilypond [] construct.

Once I figure out 'breakbefore=' so that I can concisely document it in an 
@lilypond (recent threads show me that I need to go back to the LM and re-read 
it) that as well then I'll give another draft to this patch.

So your work hasn't been in vain at all.

James