Carl Sorensen writes:
> And especially, since you care about the chord display problem, you
> have a specific reason to move to 2.15.22.
>
> Just recognize that you are moving to a development version that is
> potentially unstable (but I know of no instabilities).
My usual experience with using
On 12/21/11 11:32 AM, "Shevek" wrote:
>Carl Sorensen-3 wrote:
>>
>> This has been fixed in the development version, thanks to Adam Spiers.
>>
>> Version 2.15.21 or newer has separate properties for the suffix and the
>> bass note.
>>
>> HTH,
>>
>> Carl
>>
>
>Aha! Would you recommend upgradin
Carl Sorensen-3 wrote:
>
> This has been fixed in the development version, thanks to Adam Spiers.
>
> Version 2.15.21 or newer has separate properties for the suffix and the
> bass note.
>
> HTH,
>
> Carl
>
Aha! Would you recommend upgrading to 2.15, then?
--
View this message in context:
On 12/21/11 9:44 AM, "Shevek" wrote:
>
>
>
>James-379 wrote:
>>
>> Hello,
>>
>> On 21 December 2011 07:22, Shevek wrote:
>>>
>>> I'd like to get Lilypond's chord symbols to appear more "Real Book"
>>>like.
>>> Part of that style involves not putting a slash between the basic
>>>suffix
>>> of
James-379 wrote:
>
> Hello,
>
> On 21 December 2011 07:22, Shevek wrote:
>>
>> I'd like to get Lilypond's chord symbols to appear more "Real Book" like.
>> Part of that style involves not putting a slash between the basic suffix
>> of
>> a chord and its alterations. So far so good, as I can j
Hello,
On 21 December 2011 07:22, Shevek wrote:
>
> I'd like to get Lilypond's chord symbols to appear more "Real Book" like.
> Part of that style involves not putting a slash between the basic suffix of
> a chord and its alterations. So far so good, as I can just set
> chordNameSeparator to \mar
