[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3098 in lilypond: Parser diagnostics failing t
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3098 in lilypond: Parser diagnostics failing to recognise \on-the-fly arguments as procedure type |
Date: |
Wed, 16 Jan 2013 15:17:54 +0000 |
Comment #4 on issue 3098 by address@hidden: Parser diagnostics
failing to recognise \on-the-fly arguments as procedure type
http://code.google.com/p/lilypond/issues/detail?id=3098
The \first-page form suits my purposes here. The only thing I was noting
in comment 2 was how I got to coding it the way I did.
It was a bit of a surprise to find the standard \on-the-fly argument
procedures *not* lexically available rather than the other way around.
Maybe say something in the on-the-fly doc-string like:
(define-markup-command (on-the-fly layout props procedure arg)
(procedure? markup?)
#:category other
"Apply the @var{procedure} markup command to @var{arg}.
@var{procedure} should take a single argument.
@var{procedure} may also be coded as a LilyPond command
@var{\\procedure} @var{arg} if required."
.
.
.
But if you want to leave things as they are, that's fine by me too, as I
have my work-round to use with LyUtil.
Cheers,
Ian