Re: problem with beam collision (was: problem with cross-staff stems,?on lilypond-user)

[Graham Percival]

On Fri, Jun 10, 2011 at 07:05:34AM +0000, Keith OHara wrote:
> Janek Warchoł <lemniskata.bernoullego <at> gmail.com> writes:
> 
> > The change is almost certainly due to new beam collision algorithm.
> > I'm forwarding this message to the development team so that they will
> > know about this issue.
> > I'm not sure if it's a bug, though 
> 
> I think it is a documentation issue.  Sometimes we need to turn off the new 
> automatic collision avoidance by beams.

Our existing policy is only to document bugs which are not likely
to be fixed within a year or so.  This is to avoid having lots of
old warnings in the docs which nobody remembered to remove when
making a bug fix.

"The @knownissues should not discuss any issues that are in the
tracker, unless the issue is Priority-Postponed. The goal is to
discuss any overall architecture or syntax decisions which may be
interpreted as bugs. Normal bugs should not be discussed here,
because we have so many bugs that it would be a huge task to keep
the @knownissues current and accurate all the time."
http://lilypond.org/doc/v2.15/Documentation/contributor/section-organization


Is this problem likely to be unfixed?  Or is there a compelling
reason to override our normal doc policy in this specific case?
I am always happy to grant exceptions if there is a good reason.

Cheers,
- Graham