Re: neverBreakIf

Hi Trevor, > Ah, sorry, you're right (I'm on 2.19.15 too). You need to provide at least > one note in the score block or something that generates music output, > otherwise > there's no system (the clue's in the error message ;) =) Thanks. Looks good now. By the way… I saw the patch you submi

Re: neverBreakIf

Kieren, you wrote Sunday, October 19, 2014 7:27 PM >> That's because the commands must be within a score block to work correctly. > I believe it must have regressed by 2.19.15, which I have installed here, > since I’m still getting the ‘programming error'. Ah, sorry, you're right (I'm on 2.19.

Re: neverBreakIf

Hi Trevor, > This works fine: > > \score { > { >\displayLilyMusic \breaksOff >\displayLilyMusic \breaksOn > } > } I believe it must have regressed by 2.19.15, which I have installed here, since I’m still getting the ‘programming error'. Cheers, Kieren. ___ Kieren

Re: neverBreakIf

Kieren you wrote Sunday, October 19, 2014 6:13 PM > However, I think there’s still a problem, the one David K alluded to (but > never actually described) earlier in this thread: > > \version "2.18.2" > > pageBreaksOff = \override Score.NonMusicalPaperColumn.page-break-permission = > ##f > pageB

Re: neverBreakIf

Hi Trevor, > See https://code.google.com/p/lilypond/issues/detail?id=4169 (with > corrections!) > Thanks for prompting this. Thanks for doing that! However, I think there’s still a problem, the one David K alluded to (but never actually described) earlier in this thread: \version "2.18.2" p

Re: neverBreakIf

Hi Paul, >> Just for the record, here you've basically done this: >> x = y z >> but that only results in x = y, with z being "run" rather than being part of >> the definition of x. (See what gets logged with the snippet below.) > > Thanks! When I get a chance to run this, I will — and I’m sure

Re: neverBreakIf

Kieren, you wrote Sunday, October 19, 2014 1:00 AM > I have defined (in my layout.ly include file) the following six shortcuts, > which make typing (and remembering) easier for me: > > lineBreaksOff = \override Score.NonMusicalPaperColumn.line-break-permission = > ##f > lineBreaksOn = \overrid

Re: neverBreakIf

Hi Paul, > Hi Kieren, Just for the record, here you've basically done this: > x = y z > but that only results in x = y, with z being "run" rather than being part of > the definition of x. (See what gets logged with the snippet below.) Thanks! When I get a chance to run this, I will — and I’m

Re: neverBreakIf

ineBreaksOff \pageBreaksOff breaksOn = \lineBreaksOn \pageBreaksOn \displayLilyMusic \breaksOff \displayLilyMusic \breaksOn -- View this message in context: http://lilypond.1069038.n5.nabble.com/neverBreakIf-tp167666p167683.html Sent from the User mailing list archive at Nabble.com.

Re: neverBreakIf

Hi David, > You'll still get the programming errors for the empty systems. Haven’t so far… but I’ll be sure to check the next time I use the functions. Thanks, Kieren. ___ Kieren MacMillan, composer www: email: i...@kierenmacmillan.info

Re: neverBreakIf

Kieren MacMillan writes: > Hi David, > >> It's not a question of "having to use them". You _use_ parts of them >> without even wanting to. Loading a file containing those will output > > I’ve never gotten that error, so I went back and checked my include file… > > I actually have the definition

Re: neverBreakIf

Hi David, > It's not a question of "having to use them". You _use_ parts of them > without even wanting to. Loading a file containing those will output I’ve never gotten that error, so I went back and checked my include file… I actually have the definitions: pageBreaksOff = \override Score.No

Re: neverBreakIf

Kieren MacMillan writes: > Hi David, > >>> breaksOff = \lineBreaksOff \pageBreaksOff >>> breaksOn = \lineBreaksOn \pageBreaksOn >> >> I don't think the last two lines do what you think they do. > > Perhaps not. I’ve never had to use them, so I’m not sure! It's not a question of "having to use t

Re: neverBreakIf

Hi David, >> breaksOff = \lineBreaksOff \pageBreaksOff >> breaksOn = \lineBreaksOn \pageBreaksOn > > I don't think the last two lines do what you think they do. Perhaps not. I’ve never had to use them, so I’m not sure! Thanks, Kieren. ___ Kieren MacMillan, composer www:

Re: neverBreakIf

Kieren MacMillan writes: > Hi Frank (et al.), > >> It's somewhat strangely worded, but these commands will help you: >> \override NonMusicalPaperColumn.line-break-permission = ##f >> \override NonMusicalPaperColumn.page-break-permission = ##f > > I have defined (in my layout.ly include file) the

Re: neverBreakIf

Wow, many thanks! Frank, 2014-10-18 19:00 GMT-05:00, Kieren MacMillan : > Hi Frank (et al.), > >> It's somewhat strangely worded, but these commands will help you: >> \override NonMusicalPaperColumn.line-break-permission = ##f >> \override NonMusicalPaperColumn.page-break-permission = ##f > > I h

Re: neverBreakIf

Hi Frank (et al.), > It's somewhat strangely worded, but these commands will help you: > \override NonMusicalPaperColumn.line-break-permission = ##f > \override NonMusicalPaperColumn.page-break-permission = ##f I have defined (in my layout.ly include file) the following six shortcuts, which make

Re: neverBreakIf

Am 19.10.2014 01:43, schrieb Alicuota618: Hello, Just wondering if nobody asked for that. Because I didnt found any thread about it. I need to assign line-Breaks only where I need them. Anywhere else should never do line breaks. Unfortunately, lily breaks not only where I put \Break but everyw

neverBreakIf

Hello, Just wondering if nobody asked for that. Because I didnt found any thread about it. I need to assign line-Breaks only where I need them. Anywhere else should never do line breaks. Unfortunately, lily breaks not only where I put \Break but everywhere it needs and wants. Putting at each othe