2014-02-09 12:23 GMT+01:00 Phil Holmes <[email protected]>: > ----- Original Message ----- From: "Francisco Vila" <[email protected]> > To: "Phil Holmes" <[email protected]> > Cc: "Graham Percival" <[email protected]>; "LilyPond-Devel list" > <[email protected]>; <[email protected]> > Sent: Sunday, February 09, 2014 10:45 AM > Subject: Re: misplaced comment produces wrong HTML output. (issue 60880044) > > > >> 2014-02-09 11:23 GMT+01:00 Phil Holmes <[email protected]>: >>> >>> ----- Original Message ----- From: <[email protected]> >>> To: <[email protected]> >>> Cc: <[email protected]>; <[email protected]> >>> Sent: Sunday, February 09, 2014 10:08 AM >>> Subject: Doc: misplaced comment produces wrong HTML output. (issue >>> 60880044) >>> >>> >>>> Was this fix produced automatically by running import-lsr.py (or >>>> whatever the script is called), or was it done manually? Remember that >>>> this file begins with >>>> % DO NOT EDIT this file manually >>>> >>>> If there's a bug in the import script, then this bug will just re-appear >>>> the next time somebody imports LSR. >>>> >>>> https://codereview.appspot.com/60880044/ >>> >>> >>> >>> >>> It looks like it's actually a spurious comment in >>> Documentation/snippets/new/creating-a-delayed-turn.ly >> >> >> What's strange is that creating-a-delayed-turn.ly in >> >> Documentation/snippets/new >> >> does NOT have the spurious comment. >> >> Only creating-a-delayed-turn.ly in >> >> Documentation/snippets/ >> >> does. > > > It does have it, but in a different place, and I presume this confuses > makelsr:
Terminology issue here. The required comment is not the spurious comment. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
