In the NR 6.3.3. and 6.3.4., there are nice examples of building a music
function. The music functions are documented with standard Scheme doc
strings:
funcName =
#(define-music-function (parser location var-list) (var-types?)
"This is the doc string for the function."
return-value)
In ly/m
I don't know who's been editing NR5, but it's really nice! I was using it
to make some tweaks, and I really appreciate the improved quality it has
since a couple of years ago.
I really think that LilyPond's documentation is pretty close to excellent
now. I can find what I need and figure out how
Section NR 6.4.3, at the end of known issues and warnings, should add the
following:
"One workaround for this problem is to put the arguments into a Scheme list:
#(define-markup-command (foo layout props
arg-list)
(pair?)
...)
You could then app
I read NR 6.5.2 and couldn't understand the example. It describes the usage
of applyOutput, and presents a function for its use, but never shows how it
is applied. An actual example here would be wonderful.
N.R 6.7 shows the use of Scheme code as an articulation. The reason why
this works is un
2008/11/5 Carl D. Sorensen <[EMAIL PROTECTED]>:
> (_i "This is the doc string for the function.")
> What is the difference between these two syntaxes, and which should I use to
> add doc-strings to addChordShape, storePredefinedDiagram, pointAndClickOn,
> and pointAndClickOff, which are predefin
On 11/5/08 8:33 AM, "Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/11/5 Carl D. Sorensen <[EMAIL PROTECTED]>:
>
>> (_i "This is the doc string for the function.")
>
>> What is the difference between these two syntaxes, and which should I use to
>> add doc-strings to addChordShape, stor
2008/11/5 Carl D. Sorensen <[EMAIL PROTECTED]>:
> Thanks for answering my questions. So I guess that developers should write
> the doc strings without the _i, and the translators will add the _i when
> they translate the doc string?
... Or developers can write doc strings with _i anyway, just in
I have copied this to devel, as well as to user, because I'd like to get
permission to add the function setHeadColor to ly/music-function-init.ly.
On 11/3/08 5:51 AM, "Daniel Cheng" <[EMAIL PROTECTED]> wrote:
> It have some special feature, and I want to replicate it.
>
> See http://img235.image
On 11/5/08 8:49 AM, "Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/11/5 Carl D. Sorensen <[EMAIL PROTECTED]>:
>
>> Thanks for answering my questions. So I guess that developers should write
>> the doc strings without the _i, and the translators will add the _i when
>> they translate th
Carl
I'm partly through editing NR 5 but I broke off to try to complete NR 1.2
and other sections in NR 1 and NR 2, which I see as needing to be finished
before 2.12. No one has yet touched NR 6, apart from perhaps dumping things
in here from elsewhere. It would be really great if you could
OK, NR 6 is mine.
It won't happen very fast, but I'll work on it as I can.
Carl
On 11/5/08 12:14 PM, "Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> Carl
>
> I'm partly through editing NR 5 but I broke off to try to complete NR 1.2
> and other sections in NR 1 and NR 2, which I see as needing to
Some nitpicks during the building process, on a fresh repository:
1- the configure script:
For a long time now, I always get this:
configure: WARNING: autoconf <= 2.59 with g++ >= 3.3 gettext test broken.
configure: WARNING: Trying gcc, cross fingers.
It does not break anything; it is just bo
Hi Carl,
2008/11/5 Carl D. Sorensen <[EMAIL PROTECTED]>:
> There are some _i strings in scm/music-functions.scm, which is how I knew to
> even ask the questions.
Unfortunately, the internationalization macro doesn't work; any
function using it ends up with the description `Undocumented; FIXME'.
On 2008/11/05 20:04 +, Neil Puttock wrote:
> Unfortunately, the internationalization macro doesn't work; any
> function using it ends up with the description `Undocumented; FIXME'.
> I posted a thread about this a while ago
> (http://lists.gnu.org/archive/html/lilypond-devel/2008-07/msg00185.ht
On 2008/11/05 20:57 +0100, Jean-Charles Malahieude wrote:
> Some nitpicks during the building process, on a fresh repository:
>
>
> 1- the configure script:
> For a long time now, I always get this:
>
> configure: WARNING: autoconf <= 2.59 with g++ >= 3.3 gettext test broken.
> configure: WARNIN
Carl D. Sorensen wrote:
I have copied this to devel, as well as to user, because I'd like to get
permission to add the function setHeadColor to ly/music-function-init.ly.
Sorry for my bad English.
What I was asking is the stem directory (stem up / down),
not the color.
thank you anyway.
O
With current git:
Reading MusicXML from 00a-Basics-Pitches.xml ...
Converting to LilyPond expressions...
Traceback (most recent call last):
File "../../../scripts/musicxml2ly.py", line 2518, in
main()
File "../../../scripts/musicxml2ly.py", line 2513, in main
voices = c
17 matches
Mail list logo
