lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4954 Change s


From: Auto mailings of changes to Lily Issues
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4954 Change spanner-id to be a key instead of a string
Date: Mon, 08 Aug 2016 13:27:36 +0000


[issues:#4954] Change spanner-id to be a key instead of a string

Status: Started
Created: Mon Aug 08, 2016 01:27 PM UTC by David Kastrup
Last Updated: Mon Aug 08, 2016 01:27 PM UTC
Owner: nobody

Change spanner-id to be a key instead of a string

Also changes argument \= to be a key.

This has been taken out from the ongoing work of Nathan Chou as a
separate issue since it is a separate problem and needed a bit of
polish. There are no convert-ly rules since stuff like \=3 or
\="word" will still work due to type coercion. However, if spanner-id
has been tweaked or overridden (possible as of 2.16), the type will
now be wrong. It is rather hard to find good convert-ly rules for
those so this issue/patch currently does not try. I might try
figuring out some rules here (possibly based on pre-\= regression
tests/code) in a separate issue but they are not likely to be overly
reliable.

Backport-by: David Kastrup address@hidden

Also contains:

Changes entries for \= and in-chord slurs

http://codereview.appspot.com/306950043


Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

------------------------------------------------------------------------------
_______________________________________________
Testlilyissues-auto mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto

reply via email to

[Prev in Thread] Current Thread [Next in Thread]