lilypond-user
[Top][All Lists]
Advanced

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

Re: beam breaking in tuplets


From: Mats Bengtsson
Subject: Re: beam breaking in tuplets
Date: Mon, 06 Nov 2006 12:59:42 +0100
User-agent: Thunderbird 1.5.0.7 (X11/20060909)



Erik Sandberg wrote:
On Monday 06 November 2006 09:25, Mats Bengtsson wrote:
Victor Eijkhout wrote:
So, if you want a limited scope, you can explicitly create a short-lived
context.
Here's an example that uses smaller note heads for one measure:

\relative c'{ c d e f \new Voice {\tiny g f e d } c d e d c1 }

   /Mats

Mats, do you think it would be useful with an operator \newClone to clone the current context? E.g.
\new Staff \with {\consists Foo_engraver bar=#'baz}
 { c d \tiny  e f \newClone Staff { g f e d} c d e }
would be equivalent to:
\new Staff \with {\consists Foo_engraver bar=#'baz}
{ c d \tiny e f \new Staff \with {\consists Foo_engraver bar=#'baz} { \tiny g f e d} c d e }

(I think such operator can come out as a side-effect of some work I'm doing)
Would it even make sense to make this the default behaviour of \new?
At least, it would probably cause less surprise to a newbie than the
current implementation, in examples like:
\relative c'{ \tiny c d <<{e d} \\ {c b}>> }
On the other hand, it would probably make it less obvious for the advanced
user to predict exactly what LilyPond does, for example in situations like

\relative c' \new Voice{
 c d e f
 <<
   c1
   \new Lyrics \lyricmode {
     Some4 text
     << \new Voice \notemode { c d e2 }
        {some more text }
     >>
   }
 >>
}
where it's not obvious if the inner Voice context would inherit anything
from the outer one (maybe this is already crystal clear to you).

  /Mats




reply via email to

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