Re: convert: properly escape some single-backslashes. (issue2401042)

[percival . music . ca]

On 2010/10/12 06:23:56, dak wrote:
> mailto:address@hidden writes:

> Is that not a documentation string rather than a regexp?  And the top
> level meaning is a string meaning, anyway, not a regexp one?

Yes, sorry.  I now see that all these changes are in the
documentation strings; their effect can be seen with
  convert-ly -s

(I'm sure David already knew this, but I'm adding this info for
anybody else looking at this)

I've added \\*, which produces the output "\*Staff".  It's the same
output whether we have \* or \\*, but the latter seems to be better
style.  Thanks for catching that, and sorry it took me so long to
realize what was happening.

(if you're wondering, then yes, I made the initial patch without
realizing that the _(...) bits were doc strings -- I just saw some weird
output (due to \r), saw that other parts of that file used double
backslashes, then added them)


http://codereview.appspot.com/2401042/