Any reason why I can't continue a macro definition with a trailing
`\'?
Example:
test = \property Foo \
\property Bar
Werner
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-d
> FFF = \context PianoStaff \context Staff= dynamics \dynamicscript #"fff"
Unfortunately, this doesn't work. I get a parsing error:
piano-dynamics.ly:9:65: error: parse error:
FF = \context PianoStaff \context Staff = dynamics \dynamicscript
Hi,
The following patch includes:
* Support of hammers and pulls in tablature -- Hammers and pulls are
inserted exactly like slurs, and a "H" or a "P" is added over the slur as
needed.
The file ./input/test/tablature-hammer.ly is an example of hammer, pull and
legato in a tablature.
* Stem.up
[EMAIL PROTECTED] writes:
>
> > > > For piano music, dynamic marks are usually centered between the
> > > > left and right staff. How can I do that globally to avoid
> > > > fiddling around with extra-offset for each dynamic sign?
> >
> > See the example file input/template/piano-dynamics.ly
>
> > > For piano music, dynamic marks are usually centered between the
> > > left and right staff. How can I do that globally to avoid
> > > fiddling around with extra-offset for each dynamic sign?
>
> See the example file input/template/piano-dynamics.ly
Thanks, I had a similar idea, but this i
> > . How can I do the following easily? The accent is on *easily*,
> > of course -- I could solve it with splitted voice and turning
> > off the note heads, but this is ugly.
> >
> >| | |
> >O O O
> > 8_|
> >
> > Having an ottava line for just a s
> > Here another problem which sometimes happens. Consider a 5/4 bar
> > which contains a lot of 16ths and which must be broken across
> > staves (into 2 and 3 beats). Usually, I insert an invisible bar
> > and I'm done. But what happens with rests? If I say `R4*5', I
> > currently get a full
> > > the important observation is that \revert and \set should be
> > > seperated by some distance in time. -- takes no time.
> >
> > Indeed. But this isn't obvious for a beginner, I think. Maybe the
> > fine-tuning example could be extended to explain such things.
>
> The best solution would
