Hi, > convert-ly does text replacements. It is not a full parser. If text > replacements are supposed to work, you need to write your text in a way > that the replacement patterns cover. Stuff like putting # on one line > and a corresponding opening paren on the next line are just too weird > for those writing the conversion rules to have foreseen. > > So first try formatting your source in a somewhat common manner and then > try running convert-ly.
I did notice this way of indenting though and changed it before running Lilypond, but I didn't anticipate that convert-ly would also check for scheme code patterns. Thanks for the hint, will try this. cheers Maurits
