lilypond-user
[Top][All Lists]

## Re: What to do when \> and \< produce text

 From: Tim Reeves Subject: Re: What to do when \> and \< produce text Date: Wed, 29 Oct 2008 11:09:22 -0700

> > The \cresc macro is defined in ly/spanners-init.ly and is preceded
> by a comment:
> >
> > % STOP: junkme!
> >
> > so it's clearly not well-supported It's certainly intended to
> generate a text style crescendo "cresc.".
> > However, at the time the macro was implemented, any setting of
> crescendoText was automatically
> > reverted after the next crescendo event (i.e. it worked like a
> \once \set ...) so now that the crescendoText
> > property works just as all other properties, it would make more
> sense to let the macro be implemented as
> >
> > cresc =  {
> >  #(ly:export (make-event-chord (list cr)))
> >  \once \set crescendoText = \markup { \italic "cresc." }
> >  \once \set crescendoSpanner = #'text
> > }
> >
> > if we want it to remain. In contrast to using the supported and
> documented macro \crescTextCresc,
> > you don't get any dashed line when using \cresc. Note also that
> there is a macro \endcresc that reverts
> > the settings done by \cresc (which wouldn't be needed if we used
> the above definition).
>
> Given that what \cresc currently does can also be achieved with
>
>    \override DynamicTextSpanner #'dash-period = #-1.0
>    \crescTextCresc\
>
> as clearly shown in Notation Reference 1.3.1, it there really a need to
> keep it? I can't say that I've seen many instances of the text "cresc."
> without the dashed line, but perhaps others have.

Please don't get rid of useful functions. What is it hurting to keep it?

Tim Reeves

reply via email to