#1930 convert-ly: No rule for MMRs 'staff-position = #0

[Anonymous]

Originally created by: *anonymous

Originally created by: brownian.box@gmail.com

Since #'staff-position = #0 does not place MMR to "default position", convert-ly should at least warn on this:

\version "2.12.3"

{
  \override MultiMeasureRest #'staff-position = #0
  R1
}

Please, how _critical_ it is?

[Google Importer]

Originally posted by: brownian.box@gmail.com

(No comment was entered for this change.)

Labels: -Type-Ugly Type-Scripts

[Google Importer]

Originally posted by: simon.al...@mail.de

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

[Google Importer]

Originally posted by: dak@gnu.org

There have been a number of related issues on this.  Issue 3307, issue 3534, issue 2403.  Also several others.  It is quite likely that somewhere along the line this issue here stopped making sense.

[Google Importer]

Originally posted by: PhilEHol...@googlemail.com

Well, I guess the issue being flagged was that way back just after 2.14 was released, the behaviour of the MMR staff position over-ride changed, and therefore there could have been a convert-ly rule to "correct" this.  Sample code:

{
  R1
  \override MultiMeasureRest #'staff-position = #0
  R1
  \override MultiMeasureRest #'staff-position = #2
  R1
  \override MultiMeasureRest #'staff-position = #4
  R1
  \override MultiMeasureRest #'staff-position = #-2
  R1
}

See attached images for 2.14 and 2.16.  Rather water under the bridge, now: about 4 years ago.