Re: [Lilypond-auto] Issue 4371 in lilypond: examples need explicit \relative c'' {} to copy and paste correctly

[lilypond]

Comment #34 on issue 4371 by address@hidden: examples need explicit \relative  
c'' {} to copy and paste correctly
https://code.google.com/p/lilypond/issues/detail?id=4371

Pushed a followup fix for version numbers to staging as
commit 38876d5851add12a153f8e7adb375a8c1c84f376
Author: David Kastrup <address@hidden>
Date:   Sat Jul 18 08:18:19 2015 +0200

    Update version headers to avoid followup conversions to issue 4371

to avoid changing \relative { ... } into \relative c' { ... } when  
scripts/auxiliar/update-with-convert-ly.sh is being run.

Keith's commits were
commit 9f757add4f76eb86029405b1cf3e4d0f2fdc7ce6
Author: Keith OHara <address@hidden>
Date:   Sat Jun 27 22:20:38 2015 -0700

    Docs: remove implicit relative from translations; issue 4731

    Apply 88cfc9ee61 to tranlations.
    In order to prevent `diff` and `patch` from applying short changes
    to the wrong examples, given that the context is in different langages,
    this patch first used `sed` with
        /address@hidden/,/@end lilypond/ s/^/;/
    so each entire @lilypond example generated a diff hunk.

commit 88cfc9ee61dece9cffff98ab7f10318633698c39
Author: Keith OHara <address@hidden>
Date:   Sun May 31 19:49:54 2015 -0700

    Docs: remove implicit relative from @lilypond[verbatim]; issue 4371

    Remove the lilypond-book feature of 'relative=n' in conjunctin with
    'verbatim', so that examples cut-and-paste into user scores.

commit 085d2a54e3494826f41a3f5676bf99fc328ad71b
Author: Keith OHara <address@hidden>
Date:   Sat Jun 27 18:23:45 2015 -0700

    Docs: discourage implicit relative in lilypond[verbatim]; issue 4371


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