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

[Trevor Daniels]

Graham wrote Wednesday, October 13, 2010 4:43 AM
> Comment #3 on issue 1322 by percival.music.ca: \context must die 
> (whenever  \new can be used instead)
> http://code.google.com/p/lilypond/issues/detail?id=1322

> I took about 30 seconds to think about it.

Then spend a little longer.

> - I can't recall seeing any problems on -user that arose because 
> of  \context instead of \new.

Well, Valentin gave you one in the first comment:
http://lists.gnu.org/archive/html/bug-lilypond/2010-04/msg00090.html

> - having two different ways of doing something is no cause for 
> alarm.

It is when it leads to incorrect action as pointed out by Eluze.

> - it's less important than most priority-low items.  Issue 1245, 
> issue 673,  issue 1015, and issue 1189 are more important. 
> Admittedly it's on par with  issue 965.

This is far more serious than the removal of \new Score, which
you insisted on doing.  That was totally harmless.

> I spent a few minutes poking around in the sources, and estimate 
> that it  would take James about 5 hours.

A doc change would be a good start. We could agree on a
big @warning{}, even if not yet on what the snippets
should do, but I think a code change is needed to fix
this properly, maybe to /require/ a name on \context.

Trevor