Re: Issue 1322 in lilypond: \context must die (whenever \new can be used instead)

[lilypond]

Comment #8 on issue 1322 by v.villenave: \context must die (whenever \new  
can be used instead)
http://code.google.com/p/lilypond/issues/detail?id=1322

Carl:
> This is very convenient when combining multiple input files
> in different ways to produce multiple editions.

This is more or less what I referred to as "quite advanced and pretty  
rare". I certainly do not question the way you organise your files, and it  
is even possible that most users, when reaching a certain level, use the  
same feature. But those are not the kind of beginners asking for help on  
-user, where I've rarely seen anyone using \context appropriately.

Unlike \new, \context may produce unwanted results when used with anonymous  
contexts. I've just found an example:
http://lists.gnu.org/archive/html/bug-lilypond/2010-10/msg00245.html
You may (rightly so) object that users *should* name their contexts anyway,  
but then your "why make the user decide" question becomes "why force the  
user to name their contexts, when the parser can do without it just  
fine"? :-)

Graham:
Of course using \context Staff = "blah" is valid.  But then again, so is  
\new Score \with {foo = #bar}. Yet you've just deprecated this syntax (as I  
myself suggested a while back:  
http://lists.gnu.org/archive/html/bug-lilypond/2010-03/msg00054.html ).

I'm not suggesting that we should remove any feature. I'm just saying that  
we should encourage new users to preferably use \new, unless they really  
know what they're doing and what they need (named) \context for.