On Sat, Oct 15, 2016 at 6:38 PM, Andrew Bernard
wrote:
> Don't you have to provide an argument for \mark, I thought?
>
> I am not familiar with 2.18.2, but in 2.19.48 you do:
Yep. I think \mark requiring an argument explains the errors in the
examples fully:
- The first error it saying that the a
After playing around with Lilypond for a while, I found out that \mark
appears to "gobble up" the next token in the list. For example,
\new Staff { c \mark | c c c | }
and
\new Staff { c c c c | c c c \mark | c | c c c c | }
should give barcheck errors but don't. That's because the
13 PM
To: bug-lilypond@gnu.org
Subject: Mark / Barcheck Bug (#1626) Appearing Again
This was mentioned about five years ago, but I re-discovered it. Does the
so-called patch fix this? The bug is as follows:
Placing the \mark can have an effect on the bar check. If you run Lilypond
with the followin
This was mentioned about five years ago, but I re-discovered it. Does
the so-called patch fix this? The bug is as follows:
Placing the \mark can have an effect on the bar check. If you run
Lilypond with the following code, the barcheck will fail exactly once.
--- CCH
\new Staff { \mark | c4 c c
