Menu
▾
▴
#1269 Doc: MetronomeMark #'non-break-align-symbols should be documented
Accepted
nobody
None
evidence
Documentation
2013-04-25
2010-09-22
Anonymous
No
Originally created by: *anonymous
Originally created by: brownian.box@gmail.com
Issue 1263 should be mentioned as "known issue" in the manual and workaround should be documented.
Originally posted by: percival.music.ca@gmail.com
Why is this Critical? It's not something that worked deliberately in the past, so it's not Critical.
Labels: -Priority-Critical Priority-Medium
Originally posted by: brownian.box@gmail.com
Shouldn't any new feature be documented?
Ok, i'm fine with Medium actually :-)
Sorry. I messed something, again, probably.
Originally posted by: percival.music.ca@gmail.com
Yes, but an undocumented new feature is not a Critical issue. :)
Originally posted by: tdanielsmusic
We don't add bugs which are in the tracker to @knownissues unless they are marked postponed. There are too many of them, and it would be wasted efort if they are quickly fixed.
Trevor
Originally posted by: pkx1...@hotmail.com
So is this now invalid especially in light of
https://code.google.com/p/lilypond/issues/detail?id=1173
and
https://code.google.com/p/lilypond/issues/detail?id=1336
as this seems to be wanting to document a 'bug' (or two) which we don't do as statd in comment 4.
James
Originally posted by: pkx1...@hotmail.com
I think this is invalid. We state we don't document issues that are not postponed nor bugs which this seems to be.
James
Originally posted by: pkx1...@gmail.com
(No comment was entered for this change.)
Labels: -Priority-Medium
Originally posted by: pkx1...@gmail.com
Nothing updated on this for a year. I think (or did think when I put in the last comment) that this was invalid - request to document a bug.
This is to document as a 'known issue'
https://code.google.com/p/lilypond/issues/detail?id=1263
Originally posted by: tdanielsmusic
Closing as invalid.
The workaround for this known bug is documented in issue 1263.
Status: Invalid
Originally posted by: k-ohara5...@oco.net
Now that issue 1263 is fixed, this is no longer documenting a bug.
The property 'non-break-aligned-symbols is documented only rather poorly at
Internals Reference 3.1.71 MetronomeMark
It is effective *only* for MetronomeMarks, not for RehearsalMarks. This property can be set to '(multi-measure-rest-interface) in order to shift the MetronomeMark all the way to the left when there are full-measure rests (as shown in issue 1263, which was thought to be the request from issue 712).
Unless somebody actually wants this behavior, improving the documentation is not worth much effort.
Summary: Doc: MetronomeMark #'non-break-align-symbols should be documented
Labels: Needs-evidence
Status: Accepted