Re: Fix #915 (faulty full-bar rest positioning with clef). (issue931041)

2010-04-19 Thread n . puttock
Reviewers: carl.d.sorensen_gmail.com, Message: Hi Carl, Thanks for checking this out. On 2010/04/19 19:37:12, Carl wrote: Should the name of this property be something like ignore-prefatory-material? Hmm, possibly; it's certainly less vague. :) Actually, I've had a thought: instead of usin

Fix #915 (faulty full-bar rest positioning with clef). (issue931041)

2010-04-19 Thread Carl . D . Sorensen
Thanks, Carl http://codereview.appspot.com/931041/diff/1/9 File scm/define-grob-properties.scm (right): http://codereview.appspot.com/931041/diff/1/9#newcode756 scm/define-grob-properties.scm:756: (spacing-pair ,pair? "A pair of booleans which set the spacing for a Should the name of this pro

Re: Patch for LaTeX lilypond-syntax change

2010-04-19 Thread Graham Percival
On Mon, Apr 19, 2010 at 12:42:17PM -0600, Carl Sorensen wrote: > > On 4/19/10 11:49 AM, "David Kastrup" wrote: > > >> - we definitely need a CHANGES entry for this syntax change. > > > > I don't know how to do this one. > > Simply put an entry in Documentation/changes.tely that describes the n

Re: Patch for LaTeX lilypond-syntax change

2010-04-19 Thread Carl Sorensen
On 4/19/10 11:49 AM, "David Kastrup" wrote: > Graham Percival writes: > >> On Mon, Apr 19, 2010 at 10:54:15AM +0200, David Kastrup wrote: >>> David Kastrup writes: >>> Took a look at lilypond-book.py. Did one change and am just now recompiling. The change is fairly ob

Re: Patch for LaTeX lilypond-syntax change

2010-04-19 Thread Graham Percival
On Mon, Apr 19, 2010 at 07:49:35PM +0200, David Kastrup wrote: > Graham Percival writes: > > > A few caveats: > > - we definitely need a CHANGES entry for this syntax change. > > I don't know how to do this one. Sorry, wrong capitalization. Documentation/changes.tely Cheers, - Graham __

Re: Patch for LaTeX lilypond-syntax change

2010-04-19 Thread David Kastrup
Graham Percival writes: > On Mon, Apr 19, 2010 at 10:54:15AM +0200, David Kastrup wrote: >> David Kastrup writes: >> >> > Took a look at lilypond-book.py. Did one change and am just now >> > recompiling. >> > >> > The change is fairly obvious (hope it works): >> >> It didn't, but the followin

Re: Patch for LaTeX lilypond-syntax change (was: Rationale for LaTeX lilypond-book syntax?)

2010-04-19 Thread Graham Percival
On Mon, Apr 19, 2010 at 10:54:15AM +0200, David Kastrup wrote: > David Kastrup writes: > > > Took a look at lilypond-book.py. Did one change and am just now > > recompiling. > > > > The change is fairly obvious (hope it works): > > It didn't, but the following on Rietveld should: > > http://co

Re: staccato dots over beams

2010-04-19 Thread Werner LEMBERG
> 2. Shadow the default alist entry in default-script-alist: > > \layout { > \context { > \Score > scriptDefinitions = > #(cons > `("tenuto" > . ((script-stencil . (feta . ("tenuto" . "tenuto"))) >(quantize-position . #t) >(avoid-slur . inside)

Re: updating `\relative {' in source?

2010-04-19 Thread Mark Polesky
Mark Polesky wrote: > Okay, I updated the \relative syntax in the docs, > regtests, and scripts (there were two little instances in > the scripts/ directory). There are 37 remaining > instances; they are all in the translated docs except one > which is at the end of ly/relative-octave-music.cc. I

Patch for LaTeX lilypond-syntax change (was: Rationale for LaTeX lilypond-book syntax?)

2010-04-19 Thread David Kastrup
David Kastrup writes: > David Kastrup writes: > >> Carl Sorensen writes: >> >>> Actually, [c16 d e f] is *not* valid lilypond. The first brace needs to >>> come after the c16: >> >>> So I don't think there's a problem with the options coming after the >>> {lilypond}. >> >> Oh right. Wow. > >

Re: Rationale for LaTeX lilypond-book syntax?

2010-04-19 Thread David Kastrup
David Kastrup writes: > Carl Sorensen writes: > >> Actually, [c16 d e f] is *not* valid lilypond. The first brace needs to >> come after the c16: > >> So I don't think there's a problem with the options coming after the >> {lilypond}. > > Oh right. Wow. Took a look at lilypond-book.py. Did

Re: updating `\relative {' in source?

2010-04-19 Thread Mark Polesky
Okay, I updated the \relative syntax in the docs, regtests, and scripts (there were two little instances in the scripts/ directory). There are 37 remaining instances; they are all in the translated docs except one which is at the end of ly/relative-octave-music.cc. I modified the regex to catch m