Re: Solved: conditionals in scheme :-)

On 4/23/09 8:07 AM, "Robin Bannister" wrote: > Carl D. Sorensen wrote: >> the markup appeared different when created in what >> appeared to us to be two equivalent ways > > > In the tabClef* markups there is a baseline-skip override > just before the final \column. > > But customTabClef is

Re: Solved: conditionals in scheme :-)

Carl D. Sorensen wrote: > the markup appeared different when created in what > appeared to us to be two equivalent ways In the tabClef* markups there is a baseline-skip override just before the final \column. But customTabClef is different; it sets baseline-skip via new-props. If you make cus

Re: [PATCH] Markup commands \left-brace and \right-brace

On 4/22/09 11:19 PM, "Werner LEMBERG" wrote: > > >>> Please review this patch here: >>> >>> http://codereview.appspot.com/8874/show >> >> Looks good! > > I'm not a good lisp programmer, but isn't the standard method for > searching like that to not use a loop but recursive calls? It does

Re: \RemoveEmptyStaffContext question...

Hi Kieren, hi Nicolas, thank you very much for your replies. I am sure i can interpolate from your information to find what i need! Best, Arno Kieren MacMillan wrote: > > Hi Arno, > >> is there a way to tell lilypond in a bigger score to keep - while >> generally >> using \removeemptystaff

Re: \RemoveEmptyStaffContext question...

Hi Arno, is there a way to tell lilypond in a bigger score to keep - while generally using \removeemptystaffcontext - certain staffs unhidden, no matter whether they actualy contain music or not? The LSR contains a snippet which makes a MultiMeasureRest an "interesting" object:

Re: \RemoveEmptyStaffContext question...

Le 23 avr. 09 à 10:18, ArnoWaschk a écrit : is there a way to tell lilypond in a bigger score to keep - while generally using \removeemptystaffcontext - certain staffs unhidden, no matter whether they actualy contain music or not? You can mark a specific staff to be removable with: \new

Re: GUB3 at the lilypond-installer stage

Op woensdag 22-04-2009 om 21:07 uur [tijdzone -0700], schreef Patrick McCarty: Hi Patrick, > Your latest fixes on master work for me. > > I can now build all of the installers except for darwin-*. Attached > is the log for darwin-x86. Yes, this is a quite similar thing. While it's nice that i

\RemoveEmptyStaffContext question...

dear list, is there a way to tell lilypond in a bigger score to keep - while generally using \removeemptystaffcontext - certain staffs unhidden, no matter whether they actualy contain music or not? is there a way to tell lilypond to show staffs - while generally using \removeemptystaffcont

Re: [PATCH] Markup commands \left-brace and \right-brace

Op donderdag 23-04-2009 om 07:19 uur [tijdzone +0200], schreef Werner LEMBERG: > I'm not a good lisp programmer, but isn't the standard method for > searching like that to not use a loop but recursive calls? I don't really care about that, but it would be nice to split-out the (find-brace lambda