On Nov 27, 2005, at 9:36 PM, Bernard Hurley wrote:
On Sun, 2005-11-27 at 18:38 -0500, Michael Haynie wrote:
The change to \preLilypondExample can be made backward compatible by
defining a variable that preLilypondExample can rely on -- it's a bit
of a hack, though.
two different ideas here -- global variable above, parameter below.
Sorry about that.
Using a parameter might be worth a little breakage,
since there will not likely be a huge number of places to edit.
No it can't be made backward compatible like that, since an optional
parameter has to be declared in the definition of a macro, what
lilypond-book generates is a _call_ to the macro. However (I hadn't
thought of this in my previous post) you can get backward compatibility
by adding another command line option for lilypond-book
Having lilypond-book write two different forms of the call might be OK.
One thing, though: using 2.6.4 (on Mac OS X, at least), lilypond-book
seems to insist on parsing the --process arguments, and so complains
that -b isn't a valid option. If a patch is possible against 2.6,
that
should also be corrected.
That looks like a bug to me. It doesn't happen using 2.6.3 on Debian.
Are you sure you quoted the arguments correctly? Check it again and if
it still doesn't work email the bug list
I did, it doesn't, and I will.
I'll be delighted to test the patch.
Thanks, I have been working with 2.7.x, but I don't think lilypond-book
has changed much so I'll see what I can do!
--
Bernard Hurley <[EMAIL PROTECTED]>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
