Re: [PATCH]Re: tempoMark - documentation and use

2009-05-13 Thread Trevor Daniels
pull again. Trevor - Original Message - From: "Jonathan Kulp" To: "Trevor Daniels" Cc: "Kieren MacMillan" ; "lilypond-devel List" Sent: Wednesday, May 13, 2009 12:04 PM Subject: Re: [PATCH]Re: tempoMark - documentation and use Ugh. I have

Re: [PATCH]Re: tempoMark - documentation and use

2009-05-13 Thread Jonathan Kulp
John Mandereau wrote: Jonathan Kulp a écrit : The conflicting files are exactly the ones I modified to create the patch. True, the CG guide has a section on conflict resolution but it's not finished yet. This is true the CG is not finished, but I don't see the need to add anything to this sec

Re: [PATCH]Re: tempoMark - documentation and use

2009-05-13 Thread John Mandereau
Jonathan Kulp a écrit : The conflicting files are exactly the ones I modified to create the patch. True, the CG guide has a section on conflict resolution but it's not finished yet. This is true the CG is not finished, but I don't see the need to add anything to this section, as the referenced

Re: [PATCH]Re: tempoMark - documentation and use

2009-05-13 Thread Jonathan Kulp
John Mandereau wrote: Jonathan Kulp a écrit : Ugh. I have a merge conflict upon pulling. Did I mess up the patch? What are the conflicting files? Your patch is the last commit on master, so if Trevor applied it without amending it, the conflict is likely related to changes other than this p

Re: [PATCH]Re: tempoMark - documentation and use

2009-05-13 Thread John Mandereau
Jonathan Kulp a écrit : Ugh. I have a merge conflict upon pulling. Did I mess up the patch? What are the conflicting files? Your patch is the last commit on master, so if Trevor applied it without amending it, the conflict is likely related to changes other than this patch you made locally.

Re: [PATCH]Re: tempoMark - documentation and use

2009-05-13 Thread Jonathan Kulp
, May 13, 2009 2:32 AM Subject: [PATCH]Re: tempoMark - documentation and use Patch attached. It has patches for three different files so I just named it after the one with the most changes, working.itely. Hope there's no confusion... Jon -- Jonath

Re: [PATCH]Re: tempoMark - documentation and use

2009-05-13 Thread Trevor Daniels
Thanks Jon - pushed to origin/master Trevor - Original Message - From: "Jonathan Kulp" To: "Kieren MacMillan" Cc: "lilypond-devel List" Sent: Wednesday, May 13, 2009 2:32 AM Subject: [PATCH]Re: tempoMark - documentation and use Patch attached. It h

[PATCH]Re: tempoMark - documentation and use

2009-05-12 Thread Jonathan Kulp
Patch attached. It has patches for three different files so I just named it after the one with the most changes, working.itely. Hope there's no confusion... Jon On Tue, May 12, 2009 at 5:04 PM, Jonathan Kulp wrote: > Kieren MacMillan wrote: > IMO, we [in the docs] should *not* be encouraging t

Re: tempoMark - documentation and use

2009-05-12 Thread Jonathan Kulp
Kieren MacMillan wrote: IMO, we [in the docs] should *not* be encouraging the use of RehearsalMarks for tempo indications -- this is exactly why the \tempo command was rewritten [can't remember by whom at the moment, but "thanks!"]. In other words, this example should *also* be changed... mayb

Re: tempoMark - documentation and use

2009-05-12 Thread Kieren MacMillan
Jon, Yes! I'll change this one accordingly. Thanks, Kieren. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: tempoMark - documentation and use

2009-05-12 Thread Jonathan Kulp
Kieren MacMillan wrote: Hi Jon (et al), Now there's also a "tempoMark" function defined in NR 6.1.2, Interfaces for programmers. My instinct is to leave this one alone--it is not obsolete, since the predefined \tempo command does not take a $padding argument like this bit of scheme does, rig

Re: tempoMark - documentation and use

2009-05-12 Thread Jonathan Kulp
Mats, I tried incorporating your suggestions with mixed success. The following definition works: mpdolce = #(make-dynamic-script (markup #:hspace 0 #:translate '(5 . 0) #:line(#:dynamic "mp" #:text #:italic "dolce" ))) I changed the (cons 5 0) as you suggested, and changed hspace value to

Re: tempoMark - documentation and use

2009-05-12 Thread Mats Bengtsson
Graham Percival wrote: So should we remove (conseverywhere? That'd be easy enough to grep for. No, not in situations where you want to evaluate the values before you form the pair, like the following example from programming-interface.itely: manualBeam = #(define-music-function (par

Re: tempoMark - documentation and use

2009-05-12 Thread Graham Percival
On Tue, May 12, 2009 at 06:24:31PM +0200, Mats Bengtsson wrote: > > Jonathan Kulp wrote: >> >> mpdolce = #(make-dynamic-script (markup #:hspace 1 #:translate (cons 5 0) >> #:line(#:dynamic "mp" #:text #:italic "dolce" ))) > It seems that the above line is copied from the current documentation >

Re: tempoMark - documentation and use

2009-05-12 Thread Mats Bengtsson
Jonathan Kulp wrote: Before I make a bunch of replacements and a patch, can anyone see a potential problem with changing the example in LM 5.1.5 to use these functions instead: %% mpdolce = #(make-dynamic-script (markup #:hspace 1 #:translate (cons 5 0) #:line(#:dynamic "mp" #:text

Re: tempoMark - documentation and use

2009-05-12 Thread Kieren MacMillan
Hi Jon (et al), Now there's also a "tempoMark" function defined in NR 6.1.2, Interfaces for programmers. My instinct is to leave this one alone--it is not obsolete, since the predefined \tempo command does not take a $padding argument like this bit of scheme does, right? IMO, we [in the

Re: tempoMark - documentation and use

2009-05-12 Thread Trevor Daniels
Jonathan Kulp wrote Tuesday, May 12, 2009 6:22 AM Graham Percival wrote: > Yes, come up with another score marking. Granted, it might get [snip] I agree, that's best for the moment. Before I make a bunch of replacements and a patch, can anyone see a potential problem with changing the e

Re: tempoMark - documentation and use

2009-05-12 Thread Anthony W. Youngman
In message <4a0907a4.2080...@gmail.com>, Jonathan Kulp writes Graham Percival wrote: Yes, come up with another score marking. Granted, it might get [snip] Before I make a bunch of replacements and a patch, can anyone see a potential problem with changing the example in LM 5.1.5 to use these

Re: tempoMark - documentation and use

2009-05-11 Thread Jonathan Kulp
Graham Percival wrote: > Yes, come up with another score marking. Granted, it might get [snip] Before I make a bunch of replacements and a patch, can anyone see a potential problem with changing the example in LM 5.1.5 to use these functions instead: %% mpdolce = #(make-dynamic-script (

Re: tempoMark - documentation and use

2009-05-11 Thread Carl D. Sorensen
On 5/10/09 4:43 PM, "Anthony W. Youngman" wrote: > In message , Carl D. Sorensen > writes >> >> >> >> On 5/9/09 4:21 PM, "Anthony W. Youngman" >> wrote: >>> So - is there a function that combines stencils? Or where can I find the >>> code for \default (I did look ...) so I can try and wri

Re: tempoMark - documentation and use

2009-05-11 Thread Graham Percival
Yes, come up with another score marking. Granted, it might get obsoleted... hopefully the \mpdolce example will be obsoleted in the next few months. So perhaps this subsection should be rewritten to show how we would go about adding a new command, taking an existing one as an example. But this l

Re: tempoMark - documentation and use

2009-05-11 Thread Jonathan Kulp
Hey guys, I'm looking at this example now and am not sure what to do with it. While it's true that the tempoMark scheme function itself is not necessary now that \tempo does the same thing, it's also true that the point of this passage in the LM 5.1.5 is to show how use definitions and to place t

Re: tempoMark - documentation and use

2009-05-10 Thread Anthony W. Youngman
In message , Carl D. Sorensen writes > > > >On 5/9/09 4:21 PM, "Anthony W. Youngman" >wrote: >> So - is there a function that combines stencils? Or where can I find the >> code for \default (I did look ...) so I can try and write a defaultPlus >> function that takes a string argument ... I found

Re: tempoMark - documentation and use

2009-05-10 Thread Anthony W. Youngman
In message , Carl D. Sorensen writes On 5/9/09 4:21 PM, "Anthony W. Youngman" wrote: So - is there a function that combines stencils? Or where can I find the code for \default (I did look ...) so I can try and write a defaultPlus function that takes a string argument ... I found the LSR exa

Re: tempoMark - documentation and use

2009-05-10 Thread Carl D. Sorensen
On 5/9/09 4:21 PM, "Anthony W. Youngman" wrote: > So - is there a function that combines stencils? Or where can I find the > code for \default (I did look ...) so I can try and write a defaultPlus > function that takes a string argument ... I found the LSR example that > combines the rehearsal

Re: tempoMark - documentation and use

2009-05-10 Thread Jonathan Kulp
Graham Percival wrote: Where in the world is Carmen Sandi... oops, wrong example. If "the \tempoMark" exaple is in the NR, then Jonathan should figure out what you're talking about and prepare the patch. If "the \tempoMark" example is in the LM... then hey, this is simple enough, Jonathan shoul

Re: tempoMark - documentation and use

2009-05-10 Thread Graham Percival
Where in the world is Carmen Sandi... oops, wrong example. If "the \tempoMark" exaple is in the NR, then Jonathan should figure out what you're talking about and prepare the patch. If "the \tempoMark" example is in the LM... then hey, this is simple enough, Jonathan should still prepare a patch.

Re: tempoMark - documentation and use

2009-05-10 Thread Kieren MacMillan
Hi, The \tempoMark example should be completely rewritten to use \tempo (i.e., MetronomeMark) instead of overriding RehearsalMark -- e.g., the first entry should read mpdolce = #(make-dynamic-script (markup #:hspace 1 #:translate (cons 5 0) #:line(#:dynamic "mp" #:text #:italic "dolce"

tempoMark - documentation and use

2009-05-09 Thread Anthony W. Youngman
I've got a problem with this ... I don't know if it's been dealt with in the documentation but in the 2.12.2 manual section 4.3 (and 12.1.2), this function still uses no-spacing-rods, which 2.12 doesn't support. I was advised to use extra-spacing-width so I'm not affected, but anyone who copie