--On 05 May 2018 20:27 +1000 Andrew Bernard <andrew.bern...@gmail.com>
wrote:
> However, your file is made up of hundreds of lines like this:
>
> %Sezione M
> << {\parentheAll f,,8 bes,->~ bes,2.} \\ {s4 bes,,-. bes,,-.} >>
> << {bes,,8 f,~ f,2.} \\ {s4 f,,-. f,,-.} >> <f, f,,>8 <g, g,,>
> << {g,2.} \\ {g,,4-. g,,-.} >>
> << {g,,8_> ees,~ ees,2.} \\ {s4 ees,,-. ees,,-. r} >> ees,4-.
Interesting; I hit this problem when I used the parallel construction
for each bar of just a single page of piano music. It seemed a neat
way to write it at the time - it keeps all the notes that are together
on the page together in the text file, after all). But I learned my
lesson and now write two separate parts for each piano stave, only
resorting to this when I need a third.
> it is a type of distortion of how lilypond is normally used,
"Normally", perhaps - but looking back at my score with the problem, I
still consider it a perfectly logical way to write the music I had in
hand. In other words, I would continue to use it more if Lilypond
handled it reliably.
As someone who had a life-long career in programming, I consider this
behaviour of Lilypond to be a bug, and since the exact condition under
which it arises cannot be stated, the program has to be classified as
"unreliable" while it persists. However, as a retired person who has
no hope of getting to know this wonderful program well enough to
contribute to a fix, I just thank those who have made it and continue
to maintain and enhance it!
Paul
--
Paul Hodges
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
