Re: bleeding

2012-11-18 Thread Francisco Vila
2012/11/18 Reinhold Kainhofer : >> 2012/11/18 Reinhold Kainhofer : >> > beam is still going on. Line breaks during beams are disallowed. >> >> Not exactly, >> >> { >> \time 2/4 >> \override Beam.breakable = ##t > > Doesn't that prove my point: You have to explicitly allow breaks, because by

Re: bleeding

2012-11-18 Thread Reinhold Kainhofer
On So., 18. Nov. 2012 18:34:46 CET, Francisco Vila wrote: > 2012/11/18 Reinhold Kainhofer : > > beam is still going on. Line breaks during beams are disallowed. > > Not exactly, > > { >    \time 2/4 >    \override Beam.breakable = ##t Doesn't that prove my point: You have to explicitly allo

Re: bleeding

2012-11-18 Thread Francisco Vila
2012/11/18 Reinhold Kainhofer : > In this case, the beams are the problem: the [ is placed one note too early, > so it messes up the beaming and makes lilypond think that a beam is still > going on. Line breaks during beams are disallowed. Not exactly, { \time 2/4 \override Beam.breakable = #

Re: bleeding

2012-11-18 Thread Phil Holmes
- Original Message - From: "Marc Hohl" To: "Phil Holmes" I alerted him to the fact that the first place to look for errors is the log file, well, only if you have one ;-) If you don't, it should be on the terminal output and it should be even more obvious that the first thing to

Re: bleeding

2012-11-18 Thread Marc Hohl
Am 18.11.2012 16:52, schrieb Phil Holmes: [...] Check the output in the log file and correct the error. That was too fast, I think. The file compiles fine on my machine, the log on the console says: warning: already have a beam \clef treble bes16 d f aes bes [ c ]

Re: bleeding

2012-11-18 Thread Marc Hohl
Am 18.11.2012 16:51, schrieb Reinhold Kainhofer: On 2012-11-18 16:42, Marc Hohl wrote: Check the output in the log file and correct the error. That was too fast, I think. Nope, that's exactly the problem. The file compiles fine on my machine, the log on the console says: warning: already h

Re: bleeding

2012-11-18 Thread Phil Holmes
- Original Message - From: "Marc Hohl" To: Sent: Sunday, November 18, 2012 3:42 PM Subject: Re: bleeding Am 18.11.2012 14:58, schrieb Phil Holmes: - Original Message - From: Mark Stephen Mrotek To: lilypond-user@gnu.org Sent: Sunday, November 18, 2012 1:52

Re: bleeding

2012-11-18 Thread Reinhold Kainhofer
On 2012-11-18 16:42, Marc Hohl wrote: Check the output in the log file and correct the error. That was too fast, I think. Nope, that's exactly the problem. The file compiles fine on my machine, the log on the console says: warning: already have a beam \clef treble bes16 d f aes bes [ c ]

Re: bleeding

2012-11-18 Thread Marc Hohl
Am 18.11.2012 14:58, schrieb Phil Holmes: - Original Message - From: Mark Stephen Mrotek To: lilypond-user@gnu.org Sent: Sunday, November 18, 2012 1:52 PM Subject: bleeding Hello: How do I stop the staff from bleeding off the page? I have tried "\break." Lilypond states the command w

Re: bleeding

2012-11-18 Thread Phil Holmes
- Original Message - From: Mark Stephen Mrotek To: lilypond-user@gnu.org Sent: Sunday, November 18, 2012 1:52 PM Subject: bleeding Hello: How do I stop the staff from bleeding off the page? I have tried "\break." Lilypond states the command was overridden. Lilypond suggests using ba