James wrote: Wednesday, October 18, 2017 11:54 AM >- **status**: Started --> Invalid > - **Patch**: needs_work --> > - **Comment**: > > Revisiting this, the example given at the start of this issue > > http://lilypond.org/doc/v2.18/Documentation/notation/explicit-breaks > > has no corresponding entry at all in the 2.19 documentation. In fact the > entire NR 4.x section is completely different. > > The example in the 2.18 is for overriding when LilyPond doesn't honour a > manual `\break` or `\pagebreak` command by using > `NonMusicalPaperColumn.line-break-permission` overrides. The 2.19 doc doesn't > mention any example or even snippet. It does have one mention about > `line-break-permission` but only in the context of what the setting does and > what its defaults are.
This section was changed significantly in Oct 2014when the various \auto..breaks.. commands were installed. See https://sourceforge.net/p/testlilyissues/issues/4169/ > So I wonder now if this tracker is still needed. so marking this invalid is correct. Trevor --- This email has been checked for viruses by AVG. http://www.avg.com _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
