Re: Adds padding between Hairpins and SpanBars. (issue 5438060)

Le Dec 9, 2011 à 4:37 AM, Keith OHara a écrit : > On Thu, 08 Dec 2011 15:51:22 -0800, Thomas Morley > wrote: > >> Will this patch fix the problem drawing the hairpin under a new >> KeySignature at the line-end as shown with this example? >> >> { c'1\< \key bes\major \break >> d'2 c'\! } > >

PATCH: Countdown to 20111211

For 21:00 MST Sunday December 11 Maintainability: Issue 2026 : Make markup utility definitions available via new (scm markup-utility-defs) scheme module - R 5464045 Ugly: Issue 2057

Re: 2.12.21 regtests

Keith OHara oco.net> writes: > > ‘multi-measure-rest-standard.ly' > > ‘multi-measure-rest-tweaks.ly’ > > ‘spacing-measure-length.ly’ > > These went bad with 54495e, which I think was issue 2053, but the change > didn't show up in the regression tests posted at that issue. That is it

Re: 2.12.21 regtests

Keith OHara oco.net> writes: > Phooey. Between -20 and -21, full-measure rests are failing to get their > space again. > ‘multi-measure-rest-standard.ly' > ‘multi-measure-rest-tweaks.ly’ > ‘spacing-measure-length.ly’ These went bad with 54495e, which I think was issue 2053, but the

2.12.21 regtests

Phooey. Between -20 and -21, full-measure rests are failing to get their space again. ‘multi-measure-rest-standard.ly' ‘multi-measure-rest-tweaks.ly’ ‘spacing-measure-length.ly’ Maybe a side-effect of the changes to note-spacing (the 'extra-spacing-height rearrangements) although I wou

Re: Adds padding between Hairpins and SpanBars. (issue 5438060)

On Thu, 08 Dec 2011 15:51:22 -0800, Thomas Morley wrote: Will this patch fix the problem drawing the hairpin under a new KeySignature at the line-end as shown with this example? { c'1\< \key bes\major \break d'2 c'\! } I would have thought we wanted to have the hairpin continue under the

Re: Doc: NR improve 1.6.3 examples (issue 5448129)

LGTM http://codereview.appspot.com/5448129/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: Glossary Added x-references for grace notes (issue 5452059)

LGTM http://codereview.appspot.com/5452059/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Doc: Glossary Added x-references for grace notes (issue 5452059)

LGTM http://codereview.appspot.com/5452059/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: NR 1.2.1 Ties - added @knownissue (issue 5453066)

Looks basically good, but could use a few alterations. http://codereview.appspot.com/5453066/diff/3001/Documentation/notation/rhythms.itely File Documentation/notation/rhythms.itely (right): http://codereview.appspot.com/5453066/diff/3001/Documentation/notation/rhythms.itely#newcode528 Document

Re: Provide Scheme sandbox. (issue 5453045)

Francisco Vila writes: > 2011/12/8 : >> What you don't understand is that Emacs is no longer scanning your >> weaknesses of understanding and kneeing you in the gut whenever you do >> something as careless as typing a backspace. > > Copying/pasting from/to other programs in/from Emacs still appe

Re: center NoteColumn

Hi Harm, On Thu, Dec 8, 2011 at 6:50 PM, Thomas Morley wrote: this is great !! And I was not a little but a big blockhead.;) > Hah, no... I'm just a fresh pair of eyes :) Speaking of which, looking with fresh eyes at the file I just attached, I really should have condensed that list of nearly

Re: center NoteColumn

Hi David, 2011/12/9 David Nalesnik : > Hi Harm, > > I've taken a look at your calculations and I think I've found a more > straightforward way to determine the offsets for each of the elements. > Rather than centering each element first, then moving it with an additional > offset as you do, why no

Re: center NoteColumn

Hi Harm, I've taken a look at your calculations and I think I've found a more straightforward way to determine the offsets for each of the elements. Rather than centering each element first, then moving it with an additional offset as you do, why not simply move everything from its _original_ posi

Re: Provide Scheme sandbox. (issue 5453045)

2011/12/8 : > What you don't understand is that Emacs is no longer scanning your > weaknesses of understanding and kneeing you in the gut whenever you do > something as careless as typing a backspace. Copying/pasting from/to other programs in/from Emacs still appear in my scan. I never know when

Re: Adds padding between Hairpins and SpanBars. (issue 5438060)

Hi Mike, please excuse me disturbing the discussion. I do not understand it, so I simply ask: Will these patch fix the problem drawing the hairpin under a new KeySignature at the line-end as shown with this example? { c'1\< \key bes\major \break d'2 c'\! } (Perhaps you remember helping me t

Re: Provide Scheme sandbox. (issue 5453045)

On 2011/12/08 11:32:28, Ian Hulin (gmail) wrote: Hi David, A Scheme sandbox is a good idea, in fact it is *A Very Good Idea*. However, before we focus down on this solution, might it not be a good thing to consider this: get LilyPond in its build to provide a library of all its scheme stuff

sponsorship page

Hi all, Following a few weeks of private discussions, I have added a page for sponsorships / bounties: http://lilypond.org/sponsoring.html We may be making some small tweaks to the text on that page, and also some changes to the gitstats are on the way. People are welcome to add themselves to the

Re: Provide Scheme sandbox. (issue 5453045)

On 2011/12/08 09:07:01, dak wrote: On 2011/12/08 00:38:07, Keith wrote: > Very nice. > If you make it this easy, I might learn Scheme... > nah. Well, it is like converting people to Emacs. Those who have gotten burnt 20 years ago are a lost cause. You can't erase their childhood memories.

Re: git committish for 1 year ago

On Thu, Dec 08, 2011 at 12:25:04PM +0100, David Kastrup wrote: > > git rev-list -1 --until="1 year ago" origin Excellent, thanks! Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-d

Re: git committish for 1 year ago

David Kastrup writes: > Graham Percival writes: > >> On Thu, Dec 08, 2011 at 12:08:30PM +0100, David Kastrup wrote: >>> Graham Percival writes: >>> >>> > ~/src/lilypond$ git rev-parse "origin/master@{3 months ago}" >>> > 95fab3ca9692b197c2a26c5249d7f30b114ab451 >>> > >>> >>> Uh, @ specificati

Re: git committish for 1 year ago

Graham Percival writes: > On Thu, Dec 08, 2011 at 12:08:30PM +0100, David Kastrup wrote: >> Graham Percival writes: >> >> > ~/src/lilypond$ git rev-parse "origin/master@{3 months ago}" >> > 95fab3ca9692b197c2a26c5249d7f30b114ab451 >> > >> >> Uh, @ specifications are for the _reflog_. That is

Re: git committish for 1 year ago

On Thu, Dec 08, 2011 at 12:08:30PM +0100, David Kastrup wrote: > Graham Percival writes: > > > ~/src/lilypond$ git rev-parse "origin/master@{3 months ago}" > > 95fab3ca9692b197c2a26c5249d7f30b114ab451 > > > > Uh, @ specifications are for the _reflog_. That is something maintained > strictly loc

Re: git committish for 1 year ago

Graham Percival writes: > The command for 3 months ago is happy, but not the one for a year: > > ~/src/lilypond$ git rev-parse "origin/master@{3 months ago}" > 95fab3ca9692b197c2a26c5249d7f30b114ab451 > > ~/src/lilypond$ git rev-parse "origin/master@{1 year ago}" > warning: Log for 'origin/maste

Re: git committish for 1 year ago

2011/12/8 Francisco Vila : > 2011/12/8 Graham Percival : >> The command for 3 months ago is happy, but not the one for a year: >> >> ~/src/lilypond$ git rev-parse "origin/master@{3 months ago}" >> 95fab3ca9692b197c2a26c5249d7f30b114ab451 >> >> ~/src/lilypond$ git rev-parse "origin/master@{1 year ag

Re: git committish for 1 year ago

2011/12/8 Graham Percival : > The command for 3 months ago is happy, but not the one for a year: > > ~/src/lilypond$ git rev-parse "origin/master@{3 months ago}" > 95fab3ca9692b197c2a26c5249d7f30b114ab451 > > ~/src/lilypond$ git rev-parse "origin/master@{1 year ago}" > warning: Log for 'origin/mast

git committish for 1 year ago

The command for 3 months ago is happy, but not the one for a year: ~/src/lilypond$ git rev-parse "origin/master@{3 months ago}" 95fab3ca9692b197c2a26c5249d7f30b114ab451 ~/src/lilypond$ git rev-parse "origin/master@{1 year ago}" warning: Log for 'origin/master' only goes back to Mon, 29 Aug 2011

Re: Provide Scheme sandbox. (issue 5453045)

Reviewers: Keith, Message: On 2011/12/08 00:38:07, Keith wrote: Very nice. If you make it this easy, I might learn Scheme... nah. Well, it is like converting people to Emacs. Those who have gotten burnt 20 years ago are a lost cause. You can't erase their childhood memories. And they look w

Re: Adds padding between Hairpins and SpanBars. (issue 5438060)

Le Dec 8, 2011 à 9:37 AM, Keith OHara a écrit : > On Thu, 08 Dec 2011 00:17:56 -0800, m...@apollinemike.com > wrote: > >>> http://codereview.appspot.com/5438060/diff/2027/scm/define-grob-properties.scm#newcode1049 >>> scm/define-grob-properties.scm:1049: be drawn above and below the staff. >>>

Re: Adds padding between Hairpins and SpanBars. (issue 5438060)

On Thu, 08 Dec 2011 00:17:56 -0800, m...@apollinemike.com wrote: http://codereview.appspot.com/5438060/diff/2027/scm/define-grob-properties.scm#newcode1049 scm/define-grob-properties.scm:1049: be drawn above and below the staff. If no span bar is in a position, be drawn below and above the sta

Re: Doc: NR 1.2.1 Ties - added @knownissue (issue 5453066)

Second Draft. Thanks Keith http://codereview.appspot.com/5453066/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: NR 1.2.1 Ties - added @knownissue (issue 5453066)

Reviewers: Keith, Message: On 2011/12/07 02:21:13, Keith wrote: Looks good. For consistency with NR5.4.6 Painting objects white, you should subtract 4 from each of the layer numbers, and remove the override of StaffSymbol layer. Some people have probably used white-out on text or dynamics (

Re: Doc: NR improve 1.6.3 examples (issue 5448129)

Reviewers: dak, Message: Corrections from David. James http://codereview.appspot.com/5448129/diff/1/Documentation/notation/staff.itely File Documentation/notation/staff.itely (right): http://codereview.appspot.com/5448129/diff/1/Documentation/notation/staff.itely#newcode869 Documentation/nota

Re: Adds padding between Hairpins and SpanBars. (issue 5438060)

Le Dec 8, 2011 à 1:30 AM, k-ohara5...@oco.net a écrit : > Mike, > The old code was making a distinction between hairpins that end at the > end of a line and those that continue on the next line. > Sadly, the meaning of the boolean 'broken[]' stores at first whether > the bound on either end of a h