[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: extending \lilypondfile was: Re: Extracting header fields for use by

From: Michael Haynie
Subject: Re: extending \lilypondfile was: Re: Extracting header fields for use by e.g. LaTeX?
Date: Sat, 10 Dec 2005 21:37:21 -0500

OK, I'm back from Alaska.  Sorry for the delay.

LaTeX macros with multiple parameters typically separate them with {}, so it would look like this:


I thought we'd have lilypond-book provide the reference number, so I'm not sure what the reference would be, but I suppose that it could be provided by lilypond-book during the rewrite step. The rewrite is currently replacing the call with stuff surrounding an \input. I think I'd replace the \input with a call to yet another macro to be user defined, maybe following the \ifx pattern used by pre and post LilyPondExample. Something like:

\includeLilypondSystems{reference number}{system count}

The user would define includeLilypondSystems to e.g. discard the title, print the first system, or whatever. The main weakness that I see is that users would have to redefine the macro if they need to use several definitions in the same book. I'm not sure I know why one would want to do that, but my need to do my own titles suggests that others might need to do similarly odd things.

On Dec 2, 2005, at 8:53 AM, Bernard Hurley wrote:

On Thu, 2005-12-01 at 14:02 +0000, Bernard Hurley wrote:

This discussion, started on the "user" list. However it now seems more
appropriate for the "developer". We started discussing how header fields
might be used in lilypond-book and got on to discussing a possible
extension to \lilypondfile, with an optional extra parameter (As in
\lilypondfile[mysong{}). It should be possible for anyone
interested to pick it up from here.

Sorry it wouldn't quite work like this. Perhaps something like
would be better
Bernard Hurley <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]