Clarification for \null in \header markups

2011-03-23 Thread James Lowe
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

PATCHES: 48-hour notice for small but important fixes

2011-03-23 Thread Graham Percival
Friday, 1pm. Allow other types of staves than only Staff inside a GrandStaff http://codereview.appspot.com/4275068/ downstem 64th and 128th flag touchup http://codereview.appspot.com/4273074/ Fix 1569: Bad behavior of NoteNames context http://codereview.appspot.com/4312043/ Once those are in,

Re: Fix 1569: Bad behavior of NoteNames context (issue4312043)

2011-03-23 Thread percival . music . ca
LGTM http://codereview.appspot.com/4312043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [PATCH] Re: strange instrument name bug

2011-03-23 Thread Colin Campbell
On 11-03-23 06:17 AM, Reinhold Kainhofer wrote: Dear Haipeng, Am Mittwoch, 23. März 2011, 01:01:44 schrieb 胡海鹏 - Hu Haipeng: I meant to show a bug that the instrument name in the GrandStaff collide with the instr names in its child staves, but the following file gives no instr name in the gr

Allow other types of staves than only Staff inside a GrandStaff... (issue4275068)

2011-03-23 Thread ColinPKCampbell
Applied to 2.13.56 and shows a change in hara-kiri-tabstaff.ly Added issue #1577 on bug-lilypond to track this. http://codereview.appspot.com/4275068/ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypon

[PATCH] Re: strange instrument name bug

2011-03-23 Thread Reinhold Kainhofer
Dear Haipeng, Am Mittwoch, 23. März 2011, 01:01:44 schrieb 胡海鹏 - Hu Haipeng: > I meant to show a bug that the instrument name in the GrandStaff collide > with the instr names in its child staves, but the following file gives no > instr name in the grand staff level, although I find the engraver

Re: Adds automatic numbering to footnotes. (issue4244064)

2011-03-23 Thread m...@apollinemike.com
On Mar 22, 2011, at 7:35 PM, Neil Puttock wrote: > On 10 March 2011 10:06, m...@apollinemike.com wrote: >> On Mar 9, 2011, at 10:17 PM, n.putt...@gmail.com wrote: > >>> Does `annotation-whiteout' do anything special? If not, the existing >>> property `whiteout' should suffice. >>> >> >> It pu

Re: Fixes accidental suggestions in the beam collision engraver (issue4271054)

2011-03-23 Thread m...@apollinemike.com
On Mar 22, 2011, at 9:51 PM, Han-Wen Nienhuys wrote: > On Tue, Mar 22, 2011 at 7:54 PM, Neil Puttock wrote: >> On 22 March 2011 22:48, m...@apollinemike.com wrote: >> >>> Would an acceptable alternative be giving the TrillPitchAccidental the >>> inline-accidental-interface? >> >> Sounds good

Re: Adds automatic numbering to footnotes. (issue4244064)

2011-03-23 Thread m...@apollinemike.com
On Mar 22, 2011, at 11:28 AM, bordage.bertr...@gmail.com wrote: > Of course, I agree that we should get rid of the two-pass algorithm. But > it's really tricky to do it the clean way :o\ > I will jump on the bandwagon here in saying that I too strongly dislike the two-pass algorithm, but I disl

Re: Gets the beam collision engraver to handle autobeams (issue4287061)

2011-03-23 Thread m...@apollinemike.com
On Mar 22, 2011, at 7:22 PM, n.putt...@gmail.com wrote: > On 2011/03/20 12:00:34, MikeSol wrote: >> This is now fully functional. >> The only issue is that, for auto-beams, I don't have a good method yet > for >> keeping note-heads that are part of the beam out of the covered grobs > list. >> This