lilypond-user
[Top][All Lists]
Advanced

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

Re: lilypond manual intro


From: David Kastrup
Subject: Re: lilypond manual intro
Date: Sun, 09 Sep 2012 17:59:03 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux)

Graham Percival <address@hidden> writes:

> On Sat, Sep 08, 2012 at 09:19:36PM +0200, David Kastrup wrote:
>> Graham Percival <address@hidden> writes:
>> 
>> > (I'd also like to have an \absolute keyword so that doc examples
>> > using it could be more explicit, but that would need to wait until
>> > we have a good way to discuss syntax changes)
>> 
>> absolute =
>> #(define-music-function (parser location m) (ly:music?)
>>   #{ \transpose f f $m #})
>> 
>> \relative c' { c f b \absolute { c' d' e' } c }
>> 
>> It is not impervious against notename changes (I think I will at some
>> point work on the notename language of #{...#} to correspond to the
>> language at the time of definition rather than of use), but if required,
>> it could be written equivalently in Scheme.
>
> The point isn't to enable nesting of various \relative or
> \transpose constructs.  It's to make the notation more explicit.
> At a first glance, renaming \sequential to \absolute (or adding a
> "symlink" which means that \absolute does the same thing as
> \sequential) would achieve the goal.

No, it wouldn't, since \sequential music embedded into relative music
becomes relative.  Transposed music, in contrast, is both impervious as
well as transparent to \relative surrounding it.

-- 
David Kastrup



reply via email to

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