lilypond-devel
[Top][All Lists]
Advanced

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

Re: Make \upbow an empty command + Segmentation fault


From: Felix Janda
Subject: Re: Make \upbow an empty command + Segmentation fault
Date: Sun, 15 Jun 2014 07:45:24 +0200
User-agent: Mutt/1.5.22 (2013-10-16)

David Kastrup wrote:
> James <address@hidden> writes:
> 
> > On 12/04/14 14:22, Felix Janda wrote:
> >> Hi,
> >>
> >> say I have a violin part with bowing instructions in a variable. Now I want
> >> to use the same variable in the full orchestral score but the bowing marks
> >> should be suppressed.
> >>
> >> \upbow is treated by lilypond as an articulation, but the other
> >> articulations should be unaffected by the suppressing of \upbow.
> >>
> >> upbow={}
> >>
> >> doesn't work because it breaks things like
> >>
> >> a\upbow ~ a
> >>
> >> Playing a bit with the definition of \upbow gave me a segfault.
> >> Minimal example:
> >>
> >>
> >> \version "2.18.0"
> >>
> >> upbow = #(make-music 'ArticulationEvent
> >>                      'articulation-type "upbow" 'types #f)
> >> downbow = \upbow
> >>
> >>
> >> Anyway, how do I make a command which has no effect at all?
> 
> No effect at all in general is not feasible I think, but in this case
> you already know that it is used in post event position.  In 2.18, you
> can probably do
> 
> upbow = #(make-music 'PostEvents)
> 
> I'm not entirely sure that this will work forever as it is sort of a
> hack, but it's probably going to stick around for a while.
> 
> -- 
> David Kastrup

Thanks. That's the same thing I ended up using. (I have the faint
memory of writing a reply with this solution, but maybe I only
replied to myself...)

Felix



reply via email to

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