Graham Percival a écrit :
Good idea, but let's be careful with applying this function to existing rules: some of them may purposely contain no space at the end of the regular expression. Only people with huge LilyPond knoweledge or motivation to look around old documentation should edit existing rules to change this.Is it worth defining our own function replaceOnly("\\octave", ...) which does re.sub("\\octave[?a-z,A-Z]", ...) or whatever the regex was?I imagine that almost every convert-ly rule would benefit from "match this command, and only this command" rules, so this could save typing. And, more to the point, confusion amongst non-regex-savvy people.
Any other thoughts? John _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
