Re: [Lilypond-auto] Issue 1659 in lilypond: convert-ly should check if it's in a comment or not

[lilypond]

Updates:
        Status: Invalid
        Labels: -Frog

Comment #4 on issue 1659 by address@hidden: convert-ly should check if it's in  
a comment or not
https://code.google.com/p/lilypond/issues/detail?id=1659

Can't agree at all.  We definitely do not want the comments to go into the  
likeness of an old version.

Many convert-ly rules try to match { } as well as @{ @} in order to be able  
to convert material in the documentation outside of @lilypond blocks (where  
such quoting is unneeded).  This applies equally to comments which are  
still documentation even if not printed.

convert-ly rules should try to be specific enough that they don't match  
randomly but rather really where some stuff is intended to reflect a code  
fragment, whether inside of comments or not.  But that's a problem of the  
individual rules.

With the granularity of operation of convert-ly and with its target to be  
able with fragments of code as well as complete documents, I don't see that  
such an option makes much sense.

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