Re: Lilypond 2.19.82 with multiple voices seems to fail

[Andrew Bernard]

Hi Paul,

I have not actually said to the OP it is 'wrong', just that it's not a good
way to write, as it turns out. I knew somebody would chime in with this
exact comment. Fact is, it's completely valid code, and I pointed this out.
The issue is that it just causes problems for lilypond in reality, and
there is a more 'normal' way tor write that completely obviates the
problem. Each to his own, but I find that style very difficult to read. I
did also suggest that an addition to the NR may be a good idea.

But I know where that suggestion will lead - the NR is a reference manual,
and deliberately terse. This sort of information is tutorial in nature, and
belongs somewhere else, but I don't know where.

Also, there are good ways and bad ways to use lilypond. People are free to
do what they want. People are free to not use bar checks, and then they get
into all sorts of trouble. We cant mandate their use, but it's a really
good idea, and does no harm. Similarly in this case.

This now seems to be becoming emotionally charged, so I will depart this
thread. If the OP is interested to see another way of setting piano music,
he is welcome to contact me off list, as I have offered.

Andrew


On Sun, 3 Mar 2019 at 19:48, Paul Hodges <address@hidden> wrote:

>
>
> Now my main profession was as a computer programmer, so I well
> understand the difficulty of finding a fix for a bug like this.  I also
> appreciate that in a substantial software development which relies on
> voluntary effort (and is the most wonderful of such projects that I
> know!), this may be a thing that never gets fixed.  But an honest
> statement of that, perhaps as a warning in the documentation of the
> multiple voices feature, is what is required - rather than telling
> people that they are in some way wrong to write such a Lilypond file.
>
> Paul
>