[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Poor line break decisions
From: |
Urs Liska |
Subject: |
Re: Poor line break decisions |
Date: |
Sat, 23 Jan 2016 18:55:14 +0100 |
User-agent: |
K-9 Mail for Android |
Am 23. Januar 2016 18:51:35 MEZ, schrieb Kevin Barry <address@hidden>:
>Compiling your code on my system (fedora, 2.19.35) does not reproduce
>this
>problem. Could it be a problem with your environment? LilyPond also
>doesn't
>give any warnings in the process.
Yes, Chris, any warnings on your side (->barchecks)?
>
>On 23 January 2016 at 17:37, Chris Yate <address@hidden> wrote:
>
>> Hi,
>>
>> I'm seeing strange and unwanted line breaks in a number of scores,
>with the
>> 2.19.35 build.
>>
>> See attached PDF and zip file with input code. I suggest this is a
>bug --
>> ragged-right is OFF and it's breaking in a ridiculous place. I can
>suppress
>> this sort of thing with /noBreak but I shouldn't have to
>>
>> Before someone complains that it's not a minimal example; this sort
>of
>> issue doesn't occur with short scores... ;-)
>>
>> Thanks,
>>
>> Chris
>>
>> _______________________________________________
>> bug-lilypond mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>>
>>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>bug-lilypond mailing list
>address@hidden
>https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
- Poor line break decisions, Chris Yate, 2016/01/23
- Re: Poor line break decisions, Kevin Barry, 2016/01/23
- Re: Poor line break decisions,
Urs Liska <=
- Re: Poor line break decisions, Chris Yate, 2016/01/23
- Re: Poor line break decisions, Thomas Morley, 2016/01/23
- Re: Poor line break decisions, Chris Yate, 2016/01/23
- Re: Poor line break decisions, Thomas Morley, 2016/01/23
- Re: Poor line break decisions, Urs Liska, 2016/01/23
- Re: Poor line break decisions, Chris Yate, 2016/01/23
- Re: Poor line break decisions, Robin Bannister, 2016/01/25