[branched from -user: 'Where does "\override Score.BarNumber ..." go']
On 2010-09-03 15:41, Graham Percival wrote:
On Fri, Sep 03, 2010 at 10:16:06AM +0200, Alexander Kobel wrote:
But this makes me wonder: I vaguely remember a distinction of \score
and \new Score, which I can't find in the docs.
The distinction is that \new Score should not be used, and issue
1033 is to remove it entirely from the docs.
Hm, I see. And I recognized the potential problems.
But in the light of a consistent syntax and semantic, I see no reason
(from the users POV) to disallow it. After all, the real top-level
context is a \book {}, isn't it, and I don't see a point in disallowing
a \new Score construct just like \new Staff.
From a syntactical POV, I see the following pros for \new Score:
- You can write \with { ... } for every other context but \Score, which
(for consistency) should also work with \new Score.
- When there's a \new Foo Bar, there's also a \context Foo Bar, which
makes the same as a parallel instantiation of all Bar's.
- [Quoting Rune from
<http://www.mail-archive.com/lilypond-de...@gnu.org/msg14713.html>]:
"I know that the \score-statement is a syntactical construct, but I
think it would be nice to hide this fact from the users.
I think we could make the use of score-block much more intuitive if
changing the syntax to \new \Score and adding an implicit
sequential-statement to the score."
I think the Real Thing would be to fix \new Score s.t. it works properly
in the above manner, right?
I agree it's useful to remove all mentions from the docs for now, but I
suggest to keep a "allow \new Score" (postponed) issue there.
Cheers,
Alexander
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
