[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: |
Reinhold Kainhofer |
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:04:51 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111229 Thunderbird/9.0 |
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. This example will silently discard the outer
slur. See the attached proposed regtest.
Cheers,
Reinhold
--
------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
slur-concurrent.ly
Description: Text Data
- 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
- 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 <=
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, David Kastrup, 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
- 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