Re: Articulate.ly: Fix mordent and prall timing for short notes (issue 190530043 by botialo...@gmail.com)

On 2015/01/21 22:04:27, peter_chubb.wattle.id.au wrote: > "pkx166h" == pkx166h writes: pkx166h> On 2015/01/20 22:08:16, Peter Chubb wrote: >> articulate.ly: Fix \trillSpan problem pkx166h> Peter, I can see 4 patches uploaded here but it looks like pkx166h> fr

Re: Web: revise navigation bars with CSS gradients (issue 193140043 by paulwmor...@gmail.com)

Thanks James for committing this patch. I see that the revised CSS file is now in effect on the LilyPond website. The html remains to be updated, which will require running the website build scripts. (This will change "Main" to "LilyPond" in the main nav bar.) Also I've submitted a pull request

Re: Articulate.ly: Fix mordent and prall timing for short notes (issue 190530043 by botialo...@gmail.com)

Patchy the autobot says: passes tests. Includes a full make doc https://codereview.appspot.com/190530043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Web: revise navigation bars with CSS gradients (issue 193140043by paulwmor...@gmail.com)

- Original Message - From: "Paul Morris" To: Sent: Friday, January 23, 2015 2:39 PM Subject: Re: Web: revise navigation bars with CSS gradients (issue 193140043by paulwmor...@gmail.com) Thanks James for committing this patch. I see that the revised CSS file is now in effect on th

Retrieving information about breaks (was: Partial compilation (again))

Picking up that old thread seems better than starting a new one ... By now I've reached a different state and would like to come back to this issue with a very concrete question: Is it possible to determine at which positions (in terms of barnumber and measure-position) the final line breaks, p

Re: Web: revise navigation bars with CSS gradients (issue 193140043by paulwmor...@gmail.com)

Phil Holmes-2 wrote >> The html remains to be updated, which will require running the website >> build >> scripts. (This will change "Main" to "LilyPond" in the main nav bar.) > > The website build happens automatically. Any changes in git master that > are > part of the website get implemente

Re: Web: revise navigation bars with CSS gradients (issue193140043by paulwmor...@gmail.com)

- Original Message - From: "Paul Morris" To: Sent: Friday, January 23, 2015 3:54 PM Subject: Re: Web: revise navigation bars with CSS gradients (issue193140043by paulwmor...@gmail.com) Phil Holmes-2 wrote Also I've submitted a pull request for adding the new image files to lilypond

Re: Retrieving information about breaks (was: Partial compilation (again))

Hi Urs, On Fri, Jan 23, 2015 at 9:33 AM, Urs Liska wrote: > Picking up that old thread seems better than starting a new one ... > > By now I've reached a different state and would like to come back to this > issue with a very concrete question: > Is it possible to determine at which positions (i

Re: Retrieving information about breaks

Hi David, thanks, that works great. It did *not* write to a file, but that's not the issue here. The main point is that it listens to implicit break events. Probably the page breaks are even irrelevant for my case: finding a way to recompile individual systems. what it doesn't do yet is handl

Re: Retrieving information about breaks

Am 23.01.2015 um 18:17 schrieb Urs Liska: Hi David, thanks, that works great. It did *not* write to a file, but that's not the issue here. The main point is that it listens to implicit break events. Probably the page breaks are even irrelevant for my case: finding a way to recompile individua

Re: Retrieving information about breaks

Urs, On Fri, Jan 23, 2015 at 11:17 AM, Urs Liska wrote: > Hi David, > > thanks, that works great. > It did *not* write to a file, but that's not the issue here. > The main point is that it listens to implicit break events. > The only time it doesn't write to a file for me is when I don't save

Re: Retrieving information about breaks

Urs Liska writes: > Am 23.01.2015 um 18:17 schrieb Urs Liska: >> Hi David, >> >> thanks, that works great. >> It did *not* write to a file, but that's not the issue here. >> The main point is that it listens to implicit break events. >> >> Probably the page breaks are even irrelevant for my case:

Re: Retrieving information about breaks

Am 23.01.2015 um 18:27 schrieb David Kastrup: Urs Liska writes: Am 23.01.2015 um 18:17 schrieb Urs Liska: Hi David, thanks, that works great. It did *not* write to a file, but that's not the issue here. The main point is that it listens to implicit break events. Probably the page breaks ar

Re: Retrieving information about breaks

Urs Liska writes: > Am 23.01.2015 um 18:27 schrieb David Kastrup: >> Urs Liska writes: >> >>> Am 23.01.2015 um 18:17 schrieb Urs Liska: Hi David, thanks, that works great. It did *not* write to a file, but that's not the issue here. The main point is that it listens to i

Re: Retrieving information about breaks

On Fri, Jan 23, 2015 at 11:52 AM, David Kastrup wrote: > Urs Liska writes: > > > > > But when > > > > (ly:grob-property grob 'non-musical) > > > > evaluates to #t then > > This is about the case where > > (ly:grob-property grob 'non-musical) evaluates to '(). > > > (eq? #t (ly:grob-property grob

Re: Articulate.ly: Fix mordent and prall timing for short notes (issue 190530043 by botialo...@gmail.com)

> "pkx166h" == pkx166h writes: pkx166h> On 2015/01/21 22:04:27, peter_chubb.wattle.id.au wrote: >> > "pkx166h" == pkx166h writes: pkx166h> As and when this is ready to push, could you change the pkx166h> commit message accordingly? Again just so that everyone