lilypond-user
[Top][All Lists]
Advanced

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

Re: Invisible notes, Scheme contexts


From: Henrik Frisk
Subject: Re: Invisible notes, Scheme contexts
Date: Thu, 15 Dec 2005 10:35:13 +0100

Nicolas Sceaux <address@hidden> wrote:

> Han-Wen Nienhuys <address@hidden> writes:
> 
> > I wonder whether this should be changed too. This would mean that
> >
> >    \clef alto
> >    \clef "alto"
> >
> > becomes
> >
> >    \clef #"alto"
> >
> > or
> >
> >    \clef #'alto
> >
> > This will simplify the syntax a bit, at the expense ease of entry.
> >
> > What do you think?
> 
> I see some cases where this would be clearly a win. Few weeks ago, a
> singer asked me to change all alto clefs to treble clefs in a
> voice+piano reduction score. Just redefining the \clef music function
> would have made that really easy and quick.
> 
> The more music functions there are, and the less hardcoded syntax is,
> the more extensible and flexible LilyPond is. Ideally, even \include
> should be some kind of (not only-)music function, so that users could
> define their own \include version (for including different files
> depending on some parameters for instance, or adding a path).
> 
I agree, it sounds like a good idea.

/Henrik




reply via email to

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