Let me give an example of the bug.Regex continues from the end of the last match by default. It would be useful in some cases to be able to have a [[ https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp/global | global flag ]], which would allow the regex to find //all// possible matches. If implemented, To verify this examplethis could be activated through a checkbox in AWB, I usednext to the file menu Tools > Regex testerother (4?) checkbox settings.
==Text to search==
```
1212
```
==Regex ("Find")==
```
(\d).\1
```
==//Expected//==Default result==
(Capture groups are surrounded in curly brackets, like the formatting in AWB)
Match 1:
* Capture group 0: {121}
* Capture group 1: {1}
Match 2:
* Capture group 0: {212}==Result without global flag==
* Capture group 1: {2}
==//Actual// result==
Match 1:
* Capture group 0: {121}
* Capture group 1: {1}
==Summary==
The regex misses match 2. Presumably, this is because the match search position continues from the //end// of the last match. The correct behavior should be to continue from the next position after the //beginning// of the last match.Match 2:
* Capture group 0: {212}
* Capture group 1: {2}