#1291 R2 in single 4/4 measure produces "Object is not a markup." and "I am not spanned!"

[Anonymous]

Originally created by: *anonymous

Originally created by: brownian.box@gmail.com

Reported by Marnix Klooster and David Kastrup,
http://lists.gnu.org/archive/html/bug-lilypond/2010-10/msg00062.html
%---------------------8<-------------------------------

\version "2.12.4" % the same for 2.13.35
{ R2 }

[...]

We currently get
/tmp/junk2.ly:1:2: warning: barcheck failed at: 1/2
{
  R2 }
Preprocessing graphical objects...
programming error: Multi_measure_rest::get_rods (): I am not spanned!
continuing, cross fingers
programming error: Object is not a markup.
continuing, cross fingers
This object should be a markup: ()
programming error: Multi_measure_rest::get_rods (): I am not spanned!
continuing, cross fingers

Instead, the message better be either
Warning: multimeasure rest fails bar check
(in case that its length _is_ a full bar multiple)
or
Error: multimeasure rest size not a multiple of bar size
(in case that it could not work out anyway).

In case of a warning, error recovery needs to result in something
reasonably sensible.  If that is not feasible, one needs to create an
error instead.

A warning implies that Lilypond is going to do continue with reasonable
results.

--
David Kastrup
%---------------------8<-------------------------------

Again, not sure about priority. "barcheck failed" looks like medium; but "programming error" is closer to critical?..

[Google Importer]

Originally posted by: Carl.D.S...@gmail.com

Programming error is a graceful error, even if the message is not clear.

Critical is for segfaults, where LilyPond does not give any output before failing.

There are two deficiencies here, as I see them:

1) The error messages are very cryptic.

2) The output for R2 in 4/4 music is *not* a rest.  It's a half measure with nothing in it.

\version 2.13.46

\score {
  <<
  {R2}
  {c4 c c c}
  >>
}

Gives the attached file.

To me, this looks like a low-priority issue.

Labels: -Priority-High Priority-Low

[Google Importer]

Originally posted by: dak@gnu.org

Issue 3316 has been merged into this issue.

[Google Importer]

Originally posted by: dak@gnu.org

(No comment was entered for this change.)

Labels: -Priority-Low

[Valentin Villenave]

As part of my patch related to Issue 4375, I changed the error message to

programming error: Multi measure rest seems misplaced.

Which is at least more intelligible than getrods (): I am not spanned! (besides, that function’s no longer named get_rods).
Maybe David’s suggestion would be better, though:

multimeasure rest size not a multiple of bar size

Or for more clarity

Multi measure rest’s duration is not a multiple of the current measure length.

Thoughts?

[Trevor Daniels]

Valentin, you wrote 25/03/2020 09:48:17

As part of my patch related to Issue 4375, I changed the error message to

programming error: Multi measure rest seems misplaced.
Which is at least more intelligible than getrods (): I am not spanned! (besides, that function’s no longer named get_rods).

Maybe David’s suggestion would be better, though:

multimeasure rest size not a multiple of bar size
Or for more clarity
Multi measure rest’s duration is not a multiple of the current measure length.
Thoughts?
I prefer the last one.

Trevor