Re: [Lilypond-auto] Issue 3960 in lilypond: NR 4.3.7 - explict breaks needs better example for iine/page-break-permission

[lilypond]

Comment #2 on issue 3960 by address@hidden: NR 4.3.7 - explict breaks  
needs better example for iine/page-break-permission
http://code.google.com/p/lilypond/issues/detail?id=3960


Paul Morris
Reply | Threaded | More
Selected post Feb 25, 2014; 7:44pm
Re: Docs: example for line-break-permission and page-break-permission
Paul Morris
392 posts
        

    Trevor Daniels wrote
    However, I'm not sure that the change proposed by Paul is correct.
    I think the current wording is correct.

    Try this, and you'll see the long line runs off the right side of the  
page.
    No line break is inserted to prevent it; only the manual ones are  
actioned.

I tried this and I see what you mean.  Also this for testing pagebreak:

\paper {
  indent = #0
  ragged-right = ##t
  ragged-bottom = ##t
}

music = \relative c'' { c8 c c c c c c c }

\score {
  \new Staff {
    \repeat unfold 110 { \music }
  }
  \layout {
    \context {
      \Score
      \override NonMusicalPaperColumn.page-break-permission = ##f
    }
  }
}

No auto page breaks were inserted, the music was compressed onto one page,  
and I got these:
warning: cannot fit music on page: overflow is 27.591750
warning: compressing music to fit

So I think Trevor is right that this is an accurate statement:

"When line-break-permission is overridden to false, Lily will insert line  
breaks at explicit \break commands and nowhere else. When  
page-break-permission is overridden to false, Lily will insert page breaks  
at explicit \pageBreak commands and nowhere else."

(And if that's the case then it convinces me that what I reported in the  
other thread is indeed a bug.)

That means that this statement is potentially misleading:

"Lily sometimes rejects explicit \break and \pageBreak commands. There are  
two commands to override this behavior:"

If these commands prevent automatic breaks, then that is different from,  
and unrelated to, preventing rejecting explicit breaks.

So I like James' suggestion for a more thorough explanation that would  
remove this ambiguity.

    Trevor Daniels wrote
    Yes.  I'd remove the pagebreak from this example (since its effect is  
not
    clear in the docs anyway); use a smaller example showing a line break  
being
    inserted and being suppressed; and simply say page-break-permission
    works the same way.  I'd also give the music variable a full bar of  
notes
    rather than half a bar so the repeat counts correspond with the number
    of bars in the lines.

This makes sense to me.  Here's a smaller and more focused example:

% default output
\repeat unfold 10 { c'4 c' c' c' }

% automatic line breaks suppressed
\score {
  \new Staff {
    \repeat unfold 10 { c'4 c' c' c' }
  }
  \layout {
    \context {
      \Score
      \override NonMusicalPaperColumn.line-break-permission = ##f
    }
  }
}

Maybe a clearer name for these commands would have been:

  automatic-line-breaks = ##f
  automatic-page-breaks = ##f

-Paul

Trevor Daniels
Reply | Threaded | More
Feb 27, 2014; 9:06am
Re: Docs: example for line-break-permission and page-break-permission
Trevor Daniels
2804 posts
        

Paul Morris wrote Tuesday, February 25, 2014 7:44 PM

> That means that this statement is potentially misleading:

> "Lily sometimes rejects explicit \break and \pageBreak commands. There are
> two commands to override this behavior:"

Well, Lily does sometimes reject explicit breaks, for example when they
are placed in the middle of an incomplete bar:

  { a4 a8 a4 a \break a a a a a8 \break a4 a a a }

but the following commands do not override this behaviour.  So in this
respect the two statements are misleading.  But are there other  
circumstances
where both sentences as written are correct?  I can't think of any.

> So I like James' suggestion for a more thorough explanation that would
> remove this ambiguity.

Indeed.  I think we need a tracker to record this discussion and the
eventual conclusion.  Bug Squad: could you please set one up?

Trevor

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings