Hi all,
>>> There’s a better way — we should try to make it happen.
>> https://code.google.com/p/lilypond/issues/detail?id=3752
>> I'm not sure what it really intends to do...
> Have a \repeat coda command for repeats with coda,
> and a \repeat fine command for repeats with fine.
I agree 100% wit
Hello,
Thanks for the detailed answers. Having two scores is a way to avoid the
difficulty, but this implies that you should set bar numbers and mark numbers
manually in the second (coda) score.
Would a \once\override of layout indent and something similar to the instrument
name be a feasible
2014-12-23 17:35 GMT+01:00 Federico Bruni :
> http://www.lilypond.org/doc/v2.19/Documentation/source/Documentation/snippets/staff-notation#staff-notation-extending-glissandi-across-repeats
>
> I'm trying to edit this snippet on the LSR but I do not have the rights to
> do so.
> A fret number should
http://www.lilypond.org/doc/v2.19/Documentation/source/Documentation/snippets/staff-notation#staff-notation-extending-glissandi-across-repeats
I'm trying to edit this snippet on the LSR but I do not have the rights to
do so.
A fret number should be used for the e on second string (in bold below):
2014-12-23 16:31 GMT+01:00 Kieren MacMillan :
> Hi all,
>
> >> I'd personally avoid using stopStaff for codas.
> >> Creating a new score for the coda is much easier
> >
> > definitely a better idea, thanks
> > it's worth adding it to the LSR?
>
> It’s probably worth adding to the LSR…
>
> But I st
