[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1033 in lilypond: Documentation: \new Score must die
From: |
lilypond |
Subject: |
Re: Issue 1033 in lilypond: Documentation: \new Score must die |
Date: |
Tue, 07 Sep 2010 01:18:04 +0000 |
Comment #6 on issue 1033 by address@hidden: Documentation: \new Score
must die
http://code.google.com/p/lilypond/issues/detail?id=1033
Useful addition/clarification (I think) via private emails:
---snip--
Graham Percival wrote Monday, September 06, 2010 10:29 PM
On Mon, Sep 6, 2010 at 10:11 PM, Trevor Daniels <address@hidden>
wrote:
What, exactly, is wrong with \new Score?
The was some technical reason which prompted Han-Wen to say that
people shouldn't use it (or at least, shouldn't use it unless they
knew precisely what they were doing and could live with the
limitations / special cases).
However, I must admit that the only bits I saw about this after a few
minutes of searching were:
http://www.mail-archive.com/address@hidden/msg18300.html
http://www.mail-archive.com/address@hidden/msg14714.html
Ah, the second of these, from Mats, gives one limitation
of \new Score: it can't contain a \layout or \midi block.
I just tried, and it still honks.
So we're stuck with \score. Then to avoid confusing
duplication we have to drop \new Score. That seems to
be a reasonable argument.
Maybe it's worth asking about this on -devel again? (amusingly, I
found an email from Trevor in 2007 asking this precise question, but
it had no replies)
Seems like at least one reason was given, as above,
although maybe not as a direct reply to my question.
Trevor
--snip--
- Re: Issue 1033 in lilypond: Documentation: \new Score must die,
lilypond <=