Regex search: cannot find-prev; wrong pos for find-next

tmsg · Post by **tmsg** » 25.05.2020 10:33

Searching a text (say "local") with regex disabled works as expected. However, enabling regexes has two unhappy consequences: 1) "Find prev" is not functional anymore and (worse) b) "Find next" ALWAYS continues the search from the last found location and not from the caret, ie "Find next" has found a "local" in line 512, I then move down to line 1024 (with a "local" in the next line, 1025), "Find next" then jumps back to line 514 where there's also a "local". Disable regexes and all is well.

Post by **Alexey** » 25.05.2020 14:35

hm, it was made by design, but maybe I need to re-think this. "Find prev" is not enabled in regex engine, sorry

tmsg · Post by **tmsg** » 25.05.2020 15:00

Alexey wrote:hm, it was made by design, but maybe I need to re-think this.

By design?

So imagine a really long source code file with say 3000 lines (I tried this with one that had 3100 lines). How could you search efficiently for a regex in this file if the regex matches many lines in the file but you know that what you're looking for is somewhere after line 2500? With regex off you just go to line 2500 and start searching from there. But with regex on? Many clicks until you even get to line 2500

Alexey wrote:"Find prev" is not enabled in regex engine, sorry

Hm, that's certainly a limitation. Of the two editors I know pretty well Geany can't search regexes backwards, Akelpad can. Does "not enabled" mean it could be enabled somehow or that it's not doable at all with the regex engine you are using? This is probably not a huge problem but it still leaves me scratching my head.

tmsg · Post by **tmsg** » 26.05.2020 17:09

Well, searching with regex enabled is almost unusable as it is. The problem explained in my first post has another unhappy consequence: once a regex search has reached the end of the file there's no way (I could find) how I can ever restart the search in the beginning. What I have to do is go into the Find dialog, disable regexes and search for something non-regex once. This resets the search position for regexes. Then I have to re-enable regexes and can continue searching... this strange behaviour can't possibly be by design

Post by **Alexey** » 28.05.2020 12:40

Please try my fixes?
https://github.com/Alexey-T/CudaText/issues/2605

tmsg · Post by **tmsg** » 28.05.2020 13:52

@Alexey: So I did some very quick tests... both Find prev and searching from caret position (in both directions) now seem to work as I'd expect them to.

V good work