Re: Notes on wrong side of stem in triads

2016-10-17 3:46 GMT+02:00 DJF : > Unfortunately, I can’t reproduce the enclosed problem in a minimal example > because the same code works fine in a file by itself. "Minimal example" means that if you remove anything the problem is gone, so if the code works in what you call a

Re: No readline in scheme-sandbox

On Sun, 2016-10-16 at 23:09 +0200, David Kastrup wrote: > > David Sumbler writes: > > > > > On Sun, 2016-10-16 at 21:19 +0200, David Kastrup wrote: > > > > > > > > > David Sumbler writes: > > > > > > > > > > > > > > > > > > > Further to the above,

Re: Notes on wrong side of stem in triads

Hi Dan, At least you'll find a workaround here: http://lsr.di.unimi.it/LSR/Item?id=861 HTH. Cheers, Pierre 2016-10-17 9:48 GMT+02:00 Davide Liessi : > 2016-10-17 3:46 GMT+02:00 DJF : > > Unfortunately, I can’t reproduce the enclosed problem in a minimal

Re: Phrasing slurs shortened when broken

Javier Ruiz-Alma writes: >>> In a piece I'm working on, and only from bar 146 on, slurs which are >>> broken across systems, the first broken slur will be typeset short for >>> a reason I can't figure out.What could exclusively affect the length >>> of the first segment of

RE: Long compile times on Windows 10 status

Hi Steven, With 2.19.48 your suggestion did not work for me. With 2.19.49, it does. Since this is going to hit everybody, presumably, should it be documented in the manual somewhere folks? Can the Windows installer do something like this? I'm new to Windows, having previously led a

Trouble Combining Repeats and Closing Bars in tunes

Hi, I am looking at a 4 - part tune where the first and third parts are repeated and the second and fourth parts are not repeated. Try as I may, I cannot get Lilypond to put  the repeats and closing bars in the right place when engraving the tune. The following is just about as simple as I can

Re: Phrasing slurs shortened when broken

On 17 October 2016 at 13:00, Javier Ruiz-Alma wrote: > > The concern with fixing the first segment via \shape is the correction would > be useful when the slur is broken, but undesirable when not. We typeset the > same source with different paper sizes, so there's a real

Re: Phrasing slurs shortened when broken

Am 18. Oktober 2016 06:57:46 MESZ, schrieb Vaughan McAlley : >On 17 October 2016 at 13:00, Javier Ruiz-Alma >wrote: >> >> The concern with fixing the first segment via \shape is the >correction would be useful when the slur is broken, but

Re: lrouble Combining Repeats and Closing Bars in tunes

> -- > > Message: 2 > Date: Mon, 17 Oct 2016 23:24:51 -0400 > From: Ben Beeson > To: lilypond-user > Subject: Trouble Combining Repeats and Closing Bars in tunes > > Hi, > > I am looking at a 4 - part tune where the first

Re: Trouble Combining Repeats and Closing Bars in tunes

Am 18.10.2016 um 05:24 schrieb Ben Beeson: Hi, I am looking at a 4 - part tune where the first and third parts are repeated and the second and fourth parts are not repeated. Try as I may, I cannot get Lilypond to put the repeats and closing bars in the right place when engraving the tune. The

Re: [Spam] Re: [Spam] Re: Spanner right-hand text may disappear when padded

Rutger Hofman writes: > P.S. Building lilypond on my (up-to-date-ish but certainly not > killer-class) PC take some minutes, not those tens of hours that the > list spoke about lately. Do you want to volunteer for building our distributions and installers then? I suspect that

Re: accidentalStyle modern

Thank you very much for your hint! I will try to change laziness variable. Markus > David Wright hat am 15. Oktober 2016 um 05:29 > geschrieben: > > > On Fri 14 Oct 2016 at 06:32:11 (+0200), Pierre Perol-Schneider wrote: > > e.g. : > >

Re: [Spam] Re: [Spam] Re: Spanner right-hand text may disappear when padded

On Mon, Oct 17, 2016 at 8:26 AM, Rutger Hofman wrote: > Thanks for all the help! First I post some rationale, then my real question, > which is targeted at the developers I guess. > > The behaviour I am after is a thing I really do want: it is visually > confusing if the 'a

Re: [Spam] Re: [Spam] Re: Spanner right-hand text may disappear whenpadded

- Original Message - From: "Rutger Hofman" To: "lilypond-user" Sent: Monday, October 17, 2016 2:26 PM Subject: Re: [Spam] Re: [Spam] Re: Spanner right-hand text may disappear whenpadded P.S. Building lilypond on my (up-to-date-ish but

Re: [Spam] Re: [Spam] Re: Spanner right-hand text may disappear when padded

Thanks for all the help! First I post some rationale, then my real question, which is targeted at the developers I guess. The behaviour I am after is a thing I really do want: it is visually confusing if the 'a tempo' comes halfway the 'poco rit.)' when it is clearly meant to be after it. I

Programming error mis-predicted force

Hello all, Revisiting a score that used to compile fine some time ago with 2.19.12, running the unmodified file with 2.19.39 I get a list of programming errors the like of which I have not seen before: Preprocessing graphical objects... programming error: mis-predicted force, 143.970945

Re: Programming error mis-predicted force

Possibly https://sourceforge.net/p/testlilyissues/issues/4975/ -- Phil Holmes - Original Message - From: Andrew Bernard To: lilypond-user@gnu.org Sent: Monday, October 17, 2016 12:29 PM Subject: Programming error mis-predicted force Hello all, Revisiting a score

Re: [Spam] Re: [Spam] Re: Spanner right-hand text may disappear when padded

On Mon, Oct 17, 2016 at 9:35 AM, David Nalesnik wrote: > On Mon, Oct 17, 2016 at 8:26 AM, Rutger Hofman wrote: >> Thanks for all the help! First I post some rationale, then my real question, >> which is targeted at the developers I guess. >> >> The

Re: [Spam] Re: [Spam] Re: Spanner right-hand text may disappear when padded

On Mon, Oct 17, 2016 at 9:35 AM, David Nalesnik wrote: > On Mon, Oct 17, 2016 at 8:26 AM, Rutger Hofman wrote: >> Thanks for all the help! First I post some rationale, then my real question, >> which is targeted at the developers I guess. >> >> The

mac unstable 2.19.49

Many thanks to all who worked on the problem and found the solution. v2.19.49 seems faster than v2.19.46! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user