Re: spacing/breaking issue [time-sensitive]

2010-06-07 Thread Joe Neeman
On Mon, 2010-05-31 at 11:11 -0400, Kieren MacMillan wrote: [Lilypond 2.13.21] Hey all, I'm trying to get a score out this afternoon (for a competition deadline tomorrow!) and I'm running into a bug... Sorry, I'm on holiday and I haven't been checking email regularly, so this probably

Re: spacing/breaking issue [time-sensitive]

2010-06-07 Thread Kieren MacMillan
Hi Joe, No doubt one or more of my problems is related to the known bug regarding the missing properties blank-page-force = 0 blank-after-score-page-force = 0 but I've explicitly set that as well. Which known bug is this? I searched the bug tracker for blank and blank-page-force with

Re: spacing/breaking issue [time-sensitive]

2010-06-07 Thread Joe Neeman
On Mon, 2010-06-07 at 13:00 -0400, Kieren MacMillan wrote: Hi Joe, No doubt one or more of my problems is related to the known bug regarding the missing properties blank-page-force = 0 blank-after-score-page-force = 0 but I've explicitly set that as well. Which known bug is

spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
[Lilypond 2.13.21] Hey all, I'm trying to get a score out this afternoon (for a competition deadline tomorrow!) and I'm running into a bug... My score looks quite nice on 17 systems spread over 5 pages -- I would like: Page 1: title + 3 Pages 2-4: 4 systems Page 5: 2 systems

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Graham Percival
On Mon, May 31, 2010 at 4:11 PM, Kieren MacMillan kieren_macmil...@sympatico.ca wrote: My score looks quite nice on 17 systems spread over 5 pages -- I would like:  Page 1: title + 3  Pages 2-4: 4 systems  Page 5: 2 systems Other than manually inserting breaks, what can I do to get Lilypond

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
Hi Graham, I think that manual breaks are the easiest solution. You could separate it into distinct \bookparts, but that would be much more work than manually adding \break and \pageBreak. OK... =\ No disrespect meant to anyone, in particular Joe who has done a fabulous job increasing the

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
Hi Graham, For the record, I just added \pageBreaks where I want them... and Lilypond outputted 25 pages: it added 20 blank pages and scattered them amongst the 5 with actual music. MAO!!! =( Kieren. On 2010-May-31, at 11:36, Kieren MacMillan wrote: Hi Graham, I think that manual breaks

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Graham Percival
On Mon, May 31, 2010 at 4:41 PM, Kieren MacMillan kieren_macmil...@sympatico.ca wrote: For the record, I just added \pageBreaks where I want them... and Lilypond outputted 25 pages: it added 20 blank pages and scattered them amongst the 5 with actual music. MAO!!!  =( Stick the \pageBreak

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Neil Puttock
On 31 May 2010 16:11, Kieren MacMillan kieren_macmil...@sympatico.ca wrote: Unfortunately, minimal-breaking causes Lilypond to [try to] cram everything on one page You have to use manual breaks with minimal-breaking (though I think a bug's crept in too since 2.13.19: both regression tests for

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Graham Percival
On Mon, May 31, 2010 at 4:36 PM, Kieren MacMillan kieren_macmil...@sympatico.ca wrote: MAO MAO-ING MAO, can we please resolve these spacing issues ASAP? At the risk of making a crude masturbation joke, if I could wave a magic wand to fix stuff, I'd be waving my wand all day and night. Sorry

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
Hi Graham, Stick the \pageBreak in the 1st violin part, not the global{} part? I'm guessing here, but maybe two simultaneous \pageBreaks aren't treated/recognized as simultaneous? Thanks for the guess... but I *do* have it in only one part (by creating a separate, score-specific variable,

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
Hi Neil, Unfortunately, minimal-breaking causes Lilypond to [try to] cram everything on one page You have to use manual breaks with minimal-breaking (though I think a bug's crept in too since 2.13.19: both regression tests for minimal-breaking have started complaining). Wait... one HAS

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
Hi Graham, At the risk of making a crude masturbation joke, if I could wave a magic wand to fix stuff, I'd be waving my wand all day and night. =) For the record, there are NO KNOWN BUGS with the new spacing algorithm. So http://lists.gnu.org/archive/html/lilypond-user/2010-01/msg00086.html

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Neil Puttock
On 31 May 2010 17:07, Kieren MacMillan kieren_macmil...@sympatico.ca wrote: Wait... one HAS to use \pageBreak if you set minimal-breaking? According to the texidocs for the minimal-breaking regression tests, yes. Does that really make sense? It doesn't seem to offer anything useful over

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
Hi Neil, Wait... one HAS to use \pageBreak if you set minimal-breaking? According to the texidocs for the minimal-breaking regression tests, yes. According to Notation, The ly:minimal-breaking function performs minimal computations to calculate the page breaking: it fills a page with as many

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Alexander Kobel
On 2010-05-31 17:41, Kieren MacMillan wrote: Hi Graham, For the record, I just added \pageBreaks where I want them... and Lilypond outputted 25 pages: it added 20 blank pages and scattered them amongst the 5 with actual music. Hi, Kieren, I assume you already defined page-count = #5?

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Alexander Kobel
On 2010-05-31 19:14, Alexander Kobel wrote: On 2010-05-31 17:41, Kieren MacMillan wrote: Hi Graham, For the record, I just added \pageBreaks where I want them... and Lilypond outputted 25 pages: it added 20 blank pages and scattered them amongst the 5 with actual music. Hi, Kieren, I assume

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Nicolas Sceaux
Le 31 mai 2010 à 17:57, Neil Puttock a écrit : On 31 May 2010 16:11, Kieren MacMillan kieren_macmil...@sympatico.ca wrote: Unfortunately, minimal-breaking causes Lilypond to [try to] cram everything on one page You have to use manual breaks with minimal-breaking (though I think a bug's

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Graham Percival
On Mon, May 31, 2010 at 07:14:30PM +0200, Alexander Kobel wrote: I assume you already defined page-count = #5? There's a known issue (at least it's been on the mailing lists, no clue whether it's in the bug tracker and/or some known issues section in the docs) as follows: If page-count is

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Nicolas Sceaux
Le 31 mai 2010 à 17:11, Kieren MacMillan a écrit : [Lilypond 2.13.21] Hey all, I'm trying to get a score out this afternoon (for a competition deadline tomorrow!) and I'm running into a bug... My score looks quite nice on 17 systems spread over 5 pages -- I would like: Page 1: title

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Graham Percival
On Mon, May 31, 2010 at 08:23:40PM +0200, Nicolas Sceaux wrote: If you compile LilyPond yourself, you might try the following patch: ~~~ ... + compute_line_heights (); ROTFLMAO! That email is epic p0wnage. Given Kieren's problems trying to compile lilypond... given his

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
Hi Graham, 1) I see no indication that it was ever added to the issue tracker; hence my no KNOWN bugs still qualifies. And I don't think that we've ever claimed that we'd acknowledge bugs sent to the user list. No, the fact that the bug discussion was between two main developers does not

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
Hey Graham, ROTFLMAO! So *that's* where mao comes from... ;) That email is epic p0wnage. ;-p Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Neil Puttock
On 31 May 2010 22:29, Kieren MacMillan kieren_macmil...@sympatico.ca wrote: OK... I guess I'm just surprised that Joe didn't submit it, since it's his code, he personally confirmed/acknowledged the bug, and he appears to be a pretty conscientious dev. Hmm, are you sure this bug still

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Neil Puttock
On 31 May 2010 22:52, Neil Puttock n.putt...@gmail.com wrote: Hmm, are you sure this bug still exists?  I've just tested Reinhold's snippet from that thread, and it works fine in 2.13.23. Aha, found the fix:

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
Hi Neil, Aha, found the fix: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=337f9c142a82cc9e844ea3ce4beacfc4c24d5993 (precedes 2.13.11) Looks like Joe was pretty conscientious here. ;) I knew my faith wasn't misplaced. =) Thanks, Kieren.

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
Graham, Since none of those are in the tracker as a Critical issue, none of them are show-stoppers for 2.14. May I say that http://code.google.com/p/lilypond/issues/detail?id=884 being labelled as medium causes me to wonder about the whole bug prioritizing system. Is there some logic to what

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Graham Percival
On Mon, May 31, 2010 at 07:59:20PM -0400, Kieren MacMillan wrote: Graham, Since none of those are in the tracker as a Critical issue, none of them are show-stoppers for 2.14. May I say that http://code.google.com/p/lilypond/issues/detail?id=884 being labelled as medium causes me to

Re: spacing/breaking issue [time-sensitive]

2010-05-31 Thread Kieren MacMillan
Graham, Note that even truly embarrassing mistakes are not Critical -- those are High. I wouldn't call 884 truly embarrassing, though. But undocumented output suffixes is? At least, not in comparison to various other longstanding bugs. (are you starting to understand why I'm so