Re: [frogs] Re: Tracker 836: Add facility to change output file-name for a \book block

On Thu, Oct 29, 2009 at 06:00:06PM -0600, Carl Sorensen wrote: > > On 10/29/09 3:14 PM, "n.putt...@gmail.com" wrote: > > > I'd suggest installing emacs to sort out the indentation (even if you > > prefer to use another editor for your main work), otherwise we're going > > to spend ages pointing

Re: [frogs] Re: Tracker 836: Add facility to change output file-name for a \book block

On 10/29/09 3:14 PM, "n.putt...@gmail.com" wrote: > Hi Ian, > > I haven't commented on lily-library.scm, since there are too many > formatting issues. > > I'd suggest installing emacs to sort out the indentation (even if you > prefer to use another editor for your main work), otherwise we're

Re: Tracker 836: Add facility to change output file-name for a \book block

http://codereview.appspot.com/143055/diff/10/1005 File ly/init.ly (right): http://codereview.appspot.com/143055/diff/10/1005#newcode14 Line 14: #(define toplevel-bookparts (list)) On 2009/10/29 21:14:17, Neil Puttock wrote: trailing space Done. http://codereview.appspot.com/143055/diff/10/10

Re: [PATCH] [doc] New paper margin handling

2009/10/3 Michael Käppler : > Here you are. > The changes that aren't applied yet (default margin scaling) are already > integrated. Thanks. +...@itemize @bullet @itemize There are a few places where a full stop could do with an extra space, but the rest of the patch looks fine. You've mentio

Re: Tracker 836: Add facility to change output file-name for a \book block

Hi Ian, I haven't commented on lily-library.scm, since there are too many formatting issues. I'd suggest installing emacs to sort out the indentation (even if you prefer to use another editor for your main work), otherwise we're going to spend ages pointing out every little nitpick when we shoul

Re: convert-ly rules for the vertical layout changes

Hi Reinhold (et al), Unfortunately, I don't have the time now to investigate better defaults myself, but with these defaults, the scores simply look terrible. +1 Another problem I've found (but have yet to minimally-exemplify) is that a manual \pageBreak will often [always?] lead to a pag

Re: Tracker 836: Add facility to change output file-name for a \book block

Carl gave some feedback via e-mail. I've recorded them here before uploading a patch set. Ian http://codereview.appspot.com/143055/diff/1/5 File scm/lily-library.scm (right): http://codereview.appspot.com/143055/diff/1/5#newcode162 Line 162: (let* ( (base-name (get-current-filename parser)) r

Re: Vertical alignment of Incipits no longer working

On Thu, 2009-10-29 at 17:40 +0200, Reinhold Kainhofer wrote: > In the LSR there are two examples for incipits: > http://lsr.dsi.unimi.it/LSR/Item?id=582 > http://lsr.dsi.unimi.it/LSR/Item?id=348 > > The first one was written by Nicolas Sceaux, who generalized it to his clef- > keys.ily package to

Re: [frogs] [PATCH]: Tracker 836 - Allow output filename and output-suffix to be specified for a \book block

On 10/29/09 8:01 AM, "Ian Hulin" wrote: > Carl Sorensen wrote: >> >> >> On 10/27/09 7:05 PM, "Neil Puttock" wrote: >> >>> 2009/10/27 Carl Sorensen : >>> The patch looks good to me. Neil? >>> Not bad, Ian, but you need to keep an eye on trailing spaces and >>> indentation. >> >> To

Vertical alignment of Incipits no longer working

In the LSR there are two examples for incipits: http://lsr.dsi.unimi.it/LSR/Item?id=582 http://lsr.dsi.unimi.it/LSR/Item?id=348 The first one was written by Nicolas Sceaux, who generalized it to his clef- keys.ily package to produce critical editions showing only the original clef/key for a voice

Re: [frogs] [PATCH]: Tracker 836 - Allow output filename and output-suffix to be specified for a \book block

Carl Sorensen wrote: On 10/27/09 7:05 PM, "Neil Puttock" wrote: 2009/10/27 Carl Sorensen : The patch looks good to me. Neil? Not bad, Ian, but you need to keep an eye on trailing spaces and indentation. To try to save you time, I'm going to explain the indentation issues. +PA

Tracker 836: Add facility to change output file-name for a \book block

Reviewers: Neil Puttock, Message: This patch is now available for review. Description: Tracker 836: Add facility to change output file-name for a \book block or to set a suffix to prevent multiple files over-writing each other during a compilation. This change allows user to to this via function

convert-ly rules for the vertical layout changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since the new vertical layout engine completely changes the way the layout works, in particular, many paper variables no longer work and VerticalAxisGroup #'minimum-Y-extent also no longer works, we really need proper convert-ly rules to upgrade exi

[PATCH] Twoside mode

Hi all, please review this patch: http://codereview.appspot.com/144049 It's aim is to provide the possibility for setting different margins on odd and even pages. Regards, Michael ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.

Re: GUB: lilypond smart-autogen.sh failure

On 2009-10-29, Patrick McCarty wrote: > Hi, > > I'm getting this cryptic configure error right after arriving at the > darwin-x86::lilypond stage. > > I definitely have autoconf installed on my system, so I don't know how > the script is not finding autoconf... > > Hopefully someone can spot the

GUB: lilypond smart-autogen.sh failure

Hi, I'm getting this cryptic configure error right after arriving at the darwin-x86::lilypond stage. I definitely have autoconf installed on my system, so I don't know how the script is not finding autoconf... Hopefully someone can spot the problem. Thanks, Patrick *** Stage: autoupdate (lilyp

GUB: open/stat failure for darwin-x86::libpng

Hi, After cross/gcc succeeded, I get the attached error log for libpng. This was all done with LIBRESTRICT=open:stat. Thanks, Patrick *** Stage: configure (libpng, darwin-x86) invoking mkdir -p /home/pnorcks/git/gub/target/darwin-x86/build/libpng-1.2.8.config || true Running dump_file ('\nac

[PATCH] GUB: fix cross/gcc for darwin-x86

Hi, With luck, I finally managed to compile darwin-x86::cross/gcc with the attached patch. See the commit summary for an explanation. I could never find the source of the error, even after extensive shell tracing. :( The original report is here: http://lists.gnu.org/archive/html/lilypond-de