Re: [Lilypond-auto] Issue 1930 in lilypond: convert-ly: No rule for MMRs

lilypond-auto

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

Re: [Lilypond-auto] Issue 1930 in lilypond: convert-ly: No rule for MMRs

From:	lilypond
Subject:	Re: [Lilypond-auto] Issue 1930 in lilypond: convert-ly: No rule for MMRs 'staff-position = #0
Date:	Mon, 20 Jul 2015 21:32:00 +0000

Comment #2 on issue 1930 by address@hidden: convert-ly: No rule forMMRs 'staff-position = #0

https://code.google.com/p/lilypond/issues/detail?id=1930

I don’t quite get the aim of this; the present (2.19.23) behaviour isperfectly alright. Are you referring to versions before 2.12 havingstaff-position = #0 pointing to what is known as staff-position = 2 now?

--

You received this message because this project is configured to send allissue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[Prev in Thread]

Current Thread

[Next in Thread]

Re: [Lilypond-auto] Issue 1930 in lilypond: convert-ly: No rule for MMRs 'staff-position = #0, lilypond <=
- Message not available
  - Re: [Lilypond-auto] Issue 1930 in lilypond: convert-ly: No rule for MMRs 'staff-position = #0, lilypond, 2015/07/20
    - Message not available
    - Re: [Lilypond-auto] Issue 1930 in lilypond: convert-ly: No rule for MMRs 'staff-position = #0, lilypond, 2015/07/21

Prev by Date: Re: [Lilypond-auto] Issue 4157 in lilypond: Space left unnecessarily for key signatures on 'frenched' lines
Next by Date: Re: [Lilypond-auto] Issue 2072 in lilypond: Add proper complex variables to Lilypond
Previous by thread: Re: [Lilypond-auto] Issue 4157 in lilypond: Space left unnecessarily for key signatures on 'frenched' lines
Next by thread: Re: [Lilypond-auto] Issue 1930 in lilypond: convert-ly: No rule for MMRs 'staff-position = #0
Index(es):
- Date
- Thread