lilypond-user
[Top][All Lists]
Advanced

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

Re: Configurable Rests


From: David Kastrup
Subject: Re: Configurable Rests
Date: Fri, 21 Oct 2016 21:08:40 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

Kieren MacMillan <address@hidden> writes:

> Hi Werner,
>
>> to show you what I want:
>
> I believe the following gives the output you want:
>
> %%%  SNIPPET BEGINS
> \version "2.19"
>
> hornI = {
>   \partcombineApart
>   c''4 \once \partcombineUnisono r c'' r
>   g' \once \partcombineUnisono r c' r
>   \bar "|."
> }
>
> hornII = {
>   g'4 r g'8 r c'' r
>   r4 r e'8 g' c''4
> }
>
> \score {
>   \new Staff \with { printPartCombineTexts = ##f }
>     \partcombine #'(0 . 0) \hornI \hornII
> }
> %%%  SNIPPET ENDS
>
> Unfortunately, that may require v2.19 — I’m not sure exactly when the 
> partcombiner was improved.
> (For the record, I am using v2.19.49 for mission-critical engraving work, so 
> it’s not nearly as “unstable” as the labelling suggests.)

We had a few uglies in the early 40s.  The point in using an unstable
version is that you cannot expect to install once and forget for a year.
Depending on your luck, you may require several iterations of
reinstallation versions back and forth before you get something working
well, and you should be prepared to report new problems so that they
don't stick around for longer.  And you also have to be prepared that
brand new features you like disappear or change and you have to readapt.

I only use particularly new versions, and part of the reason is that
when something annoys me, a fix or extension tends to make it into the
code and of course it's there because I want to be using it.

-- 
David Kastrup



reply via email to

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