Strange construct

Hi, Sorry for my C++ ignorance, but what does the following do? = void performer_each (SCM list, Performer_method method) { for (SCM p = list; scm_is_pair (p); p = scm_cdr (p)) { Performer *e = dynamic_cast (unsmob_translator (scm_car (p)));

Re: GDP: consistency in @q @qq @samp @code

> I'd like to have some consistent usage amongst these terms. Here's > my proposal: > > @code{}: actual lilypond code or property/context names. > > @qq{}: only for actual quotes -- ie "he said" or "she wrote". > > @samp{}: refers to pieces of notation, such as: @samp{crescendo} is > often abbr

precomputed_recurse_over_translators

Hi, Can anybody help me with what the group of functions surrounding: precomputed_recurse_over_translators() and Translator_group::precompute_method_bindings() ...do? I start to lose the plot a bit here... Regards, Ralph ___ lilypond-devel mailing

GDP: consistency in @q @qq @samp @code

I'd like to have some consistent usage amongst these terms. Here's my proposal: @code{}: actual lilypond code or property/context names. @qq{}: only for actual quotes -- ie "he said" or "she wrote". @samp{}: refers to pieces of notation, such as: @samp{crescendo} is often abbreviated as @sam

Re: textedit protocol

Han-Wen Nienhuys wrote: 2007/10/8, Graham Percival <[EMAIL PROTECTED]>: I believe that this info is outdated, and that point-and-click info is stored in pdfs which automatically load the text editor. Or something like that; I never use point-and-click. this is not true; on mac the textedit pr

Re: textedit protocol

2007/10/8, Graham Percival <[EMAIL PROTECTED]>: > I believe that this info is outdated, and that point-and-click info is > stored in pdfs which automatically load the text editor. Or something > like that; I never use point-and-click. this is not true; on mac the textedit protocol is registered a

Re: textedit protocol

I believe that this info is outdated, and that point-and-click info is stored in pdfs which automatically load the text editor. Or something like that; I never use point-and-click. I must have had some reason for removing it two years ago, but I really can't remember that far back. Cheers,

Re: Lilypond.app for Mac OS X

2007/10/7, Julien Salort <[EMAIL PROTECTED]>: > I have a few requests however : > 1/ Would it be possible to have syntax coloring in Lilypond.app's editor ? > I suppose you could even take the code from other opensource's projects > like TeXShop or iTeXMac since > Lilypond has kind of a LaTeX-like

textedit protocol

It seems that from LP version 2.6 to 2.7, the information on how to configure the web browser for the textedit protocol (to achieve point-and-click) dissapeared from the docs. Am I looking at the wrong place? If it did, is it suppossed to be something clear for the average user? See http://lily

Re: Caesura, n-th time :)

Werner LEMBERG schrieb: ... Basically, you are right, however, we have already to think about backwards compatibility... Good point. This made me think that in case my recent patch is applied, maybe convert-ly (or rather convertrules.py) should be updated, too!? Just in case I'm sending a pa

Microtone accidentals

Hi everyone, here is the last and biggest unfinished project that has been resting on my hard drive for a while: Arrowed accidentals for microtone notation. At present Lilypond already has good support for quarter- and other microtones (see, e.g., section 6.1.4 of the manual or the NEWS file of