Re: [Lilypond-auto] Issue 3487 in lilypond: Patch: Make several special characters with or without backslash "shorthands"

[lilypond]

Updates:
        Status: Fixed
        Labels: -Patch-push Fixed_2_17_25

Comment #17 on issue 3487 by address@hidden: Patch: Make several special  
characters with or without backslash "shorthands"
http://code.google.com/p/lilypond/issues/detail?id=3487

Pushed to staging as a merge commit
*   commit 50b7d56d80c5842ce9bce3bcebe6b0491e37cee3
|\  Merge: 61275ff 65e12a8
| | Author: David Kastrup <address@hidden>
| | Date:   Wed Aug 14 09:22:16 2013 +0200
| |
| |     Merge branch 'issue3487'
| |
| |     Done as a merge commit because of invalid intermediate stages before
| |     running scripts/auxiliar/update-with-convert-ly.sh
| |
| * commit 65e12a858de67b4d061c9fb595b81024fe22c6cf
| | Author: David Kastrup <address@hidden>
| | Date:   Fri Aug 9 18:55:12 2013 +0200
| |
| |     Make regtest for shorthands (Issue 3487)
| |
| * commit 48a57a1c8feb426029e059d9fbf8aaf1b14f0ff8
| | Author: David Kastrup <address@hidden>
| | Date:   Tue Aug 6 21:34:01 2013 +0200
| |
| |     Run scripts/auxiliar/update-with-convert-ly.sh
| |
| * commit 5c58da93f8859c3f15760631db4e63590e073e1e
| | Author: David Kastrup <address@hidden>
| | Date:   Sun Aug 4 11:32:09 2013 +0200
| |
| |     Issue 3487: Make several special characters with or without  
backslash "shorthands"
| |
| |     Single non-alphanumeric ASCII characters not requiring special
| |     treatment in lexer or parser can now be redefined like escaped
| |     identifiers.  The same holds for escaped non-alphanumeric ASCII
| |     characters.  The identifying name you use for redefining them is the
| |     string corresponding to the full shorthand, in contrast to escaped
| |     identifiers where the identifying name omits the initial backslash.
| |
| |     Notable shorthands not treated specially in the parser (some of them
| |     newly so) can be seen in the following definitions from
| |     scm/declarations-init.ly:
| |
| |     "|" = #(make-music 'BarCheck)
| |     "[" = #(make-span-event 'BeamEvent START)
| |     "]" = #(make-span-event 'BeamEvent STOP)
| |     "~" = #(make-music 'TieEvent)
| |     "(" = #(make-span-event 'SlurEvent START)
| |     ")" = #(make-span-event 'SlurEvent STOP)
| |     "\\!" = #(make-span-event 'CrescendoEvent STOP)
| |     "\\(" = #(make-span-event 'PhrasingSlurEvent START)
| |     "\\)" = #(make-span-event 'PhrasingSlurEvent STOP)
| |     "\\>" = #(make-span-event 'DecrescendoEvent START)
| |     "\\<" = #(make-span-event 'CrescendoEvent START)
| |     "\\[" = #(make-span-event 'LigatureEvent START)
| |     "\\]" = #(make-span-event 'LigatureEvent STOP)
| |     "\\~" = #(make-music 'PesOrFlexaEvent)
| |     "\\\\" = #(make-music 'VoiceSeparator)
| |
| * commit a7c14a5a83ddf2926895aa40cfdf50e7dcebf53c
| | Author: David Kastrup <address@hidden>
| | Date:   Sun Aug 4 12:21:09 2013 +0200
| |
| |     Replace staccatissimo shorthand -| with -!
| |
| |     The bar line character is used too prominently, and ! seems more  
appropriate.
| |
| * commit 51697e92e7deb4281b6602928f7bbd3e99ee7b36
|/  Author: David Kastrup <address@hidden>
|   Date:   Sun Aug 4 11:36:34 2013 +0200
|
|       Make tempo range \tempo 20~30 be input as \tempo 20-30 instead
|
|       \tempo's use of ~ was rather untypical for LilyPond.  Letting it
|       rather use @code{-} for ranges leaves just a single use for ties,
|       making it feasible to make @code{~} definable by the user in a later
|       commit.
|


--
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