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 solution? A happy end of the year! JM > Le 23 déc. 2014 à 16:55, David Kastrup <d...@gnu.org> a écrit : > > Federico Bruni <fedel...@gmail.com> writes: > >> 2014-12-23 16:31 GMT+01:00 Kieren MacMillan <kieren_macmil...@sympatico.ca>: >> >>> 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 strongly disagree with the suggestion that it’s a "better solution”: >>> it divides a single musical “piece” (work, expression, whatever) into two >>> separate scores just to accomplish an engraving issue which should be as >>> easy as using \repeat volta. Now everything (e.g., parts, midi, etc.) >>> requires double-scoring or recombining of variables, etc. >>> >>> There’s a better way — we should try to make it happen. >>> >>> >> Do we have an issue for this? >> This is the only one I could find: >> https://code.google.com/p/lilypond/issues/detail?id=3752 >> >> and 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 thought that was obvious. If you find > that the problem description is deficient, please add a comment to the > issue. > > -- > David Kastrup > > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
