[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no longer work |
Date: |
Fri, 22 Nov 2013 14:59:05 +0000 |
Updates:
Status: Fixed
Labels: -Patch-push -Backport_2_18_0 Fixed_2_17_96
Comment #9 on issue 3665 by address@hidden: transposing \chords does no longer
work
http://code.google.com/p/lilypond/issues/detail?id=3665
Pushed to stable/2.18 as
commit eee326f68c162fa8c74e810d7cf7fbf00e2ed5df
Author: David Kastrup <address@hidden>
Date: Fri Nov 15 17:58:55 2013 +0100
Let simple_music possibly return a pitch in \chordmode
commit 3346fe361ea3e597874f95063f6f27845d4fff5c
Author: David Kastrup <address@hidden>
Date: Sat Nov 16 16:23:59 2013 +0100
Make sure optional arguments accepted as pitches stay pitches when
reparsing
commit e66e5da1017acb315bdfece931c2494515b10a87
Author: David Kastrup <address@hidden>
Date: Sat Nov 16 13:24:11 2013 +0100
Let a PITCH_IDENTIFIER optionally be followed by octave modifiers
This makes pitch identifiers more similar to note names. There is no
point in keeping the distinction just for triggering syntax errors
on music that has no sensible other interpretation.
commit b90102932bafdf5ba49b732155c2895fdb525b98
Author: David Kastrup <address@hidden>
Date: Fri Nov 15 17:36:49 2013 +0100
Make make_music_from_simple return music rather than a list in
\chordmode
commit eb897bc555df42efc0d5b0ab448b1f479ac0a81b
Author: David Kastrup <address@hidden>
Date: Sat Nov 16 14:09:53 2013 +0100
parser: move FRACTION into embedded_scm_bare_arg
It's a closed expression; not having to parse it with separate rules
reduces the amount of cruft in the rules.
commit e36d7910ea40dfccec23c8ffc443cd52fd1f98e9
Author: David Kastrup <address@hidden>
Date: Sat Nov 16 12:50:42 2013 +0100
Fold function_arglist_backup_common into function_arglist_backup
After the last refactoring, function_arglist_backup does not need a
closed
variant, so there is no point in an extra non-terminal.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
- [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no longer work, lilypond, 2013/11/15
- Re: [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no longer work, lilypond, 2013/11/16
- Re: [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no longer work, lilypond, 2013/11/16
- Re: [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no longer work, lilypond, 2013/11/16
- Re: [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no longer work, lilypond, 2013/11/19
- Re: [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no longer work, lilypond, 2013/11/19
- Re: [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no longer work, lilypond, 2013/11/19
- Re: [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no longer work, lilypond, 2013/11/22
- Re: [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no longer work,
lilypond <=
- Re: [Lilypond-auto] Issue 3665 in lilypond: transposing \chords does no longer work, lilypond, 2013/11/24