Brickgard opened this issue a year ago · 1 comments
In the latest versions (first observed after migrating from 1.7.3 to 2.0.0+) Find and Replace next advances to the next entry before replacing.
This behavior results in repeated "find and replace" actions replacing every other match.
I'll look into it later