I'm updating my theme with new versions of most modules. I've upgraded from textedit 2.1l to 2.4l-13. But now my textreplace bangs have stopped working.

I've updated my code so that what was...

is now...


Is there another change that has been made to textedit that I'm forgetting to include?

[Build 11]
...
Backwardly compatible now.
New syntax only used if you specify TextEditNewSyntax (boolean) - default is old syntax (i.e. " ")

Thanks doy, but still no luck. Well, maybe a little bit. I tried running the textreplace as a bang through lsxcommand. I found that this code worked...

... but this did not ...


Can anyone confirm whether or not textedit handles replacements of integers differently to previous versions?

Well I found it.


All my variables use underscores.

Textedit is perhaps the worst example of logical handling of stings I've ever seen.

@ replace "
\= for "
\~ for ;
\@ for @
\/ for \\
\[ for current build number
* was \& but now it's \>
eol $ became # which in turn became _
And with the very latest version I see \- is for _

Am I the only one who thinks this is nuts? Regexp is hard enough without introducing bazaar escape codes that change with every release. AFAIK Java, C++, PHP, MySQL all use the same standard for regexp. Perhaps it is unavoidable for textedit to do it this way.

I'll bet that 99% of the stuff that textedit is used for could be handled by saving vars with mzscript. It might take a bit more creativity, but I'm almost sure it's probably possible.

but then I've never used textedit...

I think I'll explore that option. Thanks, RabidCow.

LOL:
This couldn't work because you have one string (hotspots_on *) associated with \1 and textedit think you want to replace it with an undefined string \10 !!!

Why not simply do:
or

all of the special characters (like _) can be used by putting a \ in front of them...