[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the s
From: |
David Kastrup |
Subject: |
Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning |
Date: |
Wed, 15 Feb 2012 19:18:05 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) |
Reinhold Kainhofer <address@hidden> writes:
> On 15/02/2012 17:01, address@hidden wrote:
>> Updates:
>> Labels: Patch-new
>>
>> Comment #21 on issue 1967 by address@hidden: Concurrent slurs that start
>> and end at the same moment should not produce a warning
>> http://code.google.com/p/lilypond/issues/detail?id=1967#c21
>>
>> Allow multiple identical slurs (issue 1967).
>
> It allows also non-identical slurs, e.g. { c4(( c) d f) }, which is a
> common error for ties.
Where is the problem with that? Both ties start at the same place, so
you can't confuse their nesting.
> This example will silently discard the outer slur.
The number of times where I have to contradict you today is impressive.
No, it won't. Both get typeset.
--
David Kastrup
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, (continued)
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, David Kastrup, 2012/02/16
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/18
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, Reinhold Kainhofer, 2012/02/15
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning,
David Kastrup <=
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, Reinhold Kainhofer, 2012/02/15
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, Reinhold Kainhofer, 2012/02/15