Quote:
Originally Posted by DiapDealer
I've had the issue with the replacement strings being "\1" or "\1\2" instead of the proper contents of the backreferences since 0.5.1 as well. But it's very inconsistent and I haven't been able to track down the exact circumstances under which it happens.
|
Quote:
Originally Posted by Timur
The problem mmat1 and ElMiko described(back references not resolving for some instances and replacing with back reference text itself, while doing step-by-step replacement) happened to me in 0.5.1 as well. Windows 7, 64-bit.
|
Found/fixed the issue. It only happens with Replace in All HTML Files, and only if you are at the bottom of one file and hit Replace to go find the first match in the top of the next file - when you hit Replace again it leaves the \1\2 items instead of doing the replace because the location of the last found text info wasn't being updated correctly.
As a workaround, if your Replace goes to the next page, just click on the beginning of the file and do the Replace again.
I actually didn't see this at first because I already had it working in my version as part of implementing the new Spell Check find - after fixing what I thought was a new issue.