https://bugs.kde.org/show_bug.cgi?id=497875

Kåre Särs <kare.s...@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
                 CC|                            |kare.s...@iki.fi
             Status|REPORTED                    |CONFIRMED

--- Comment #2 from Kåre Särs <kare.s...@iki.fi> ---
I can confirm that we have a problem here...

The problem seems to be that the text range that we store, to prevent replacing
already edited text, does not contain the lookahead/behind. And since that then
does not match with the regular expression, it bails out.

Now the question is how do we solve the problem? How do we get enough context
around the saved range? A single character (or fixed N), would be doable, but
that does not scale very much. And rechecking the whole while line might be
problematic. what if we have multiple matches on the same line. Which should we
replace?

One solution could be to strip the lookahead/behind for the replacement
validity check regex..., but then if the text around the match has changed to
no longer match the original regex, we get a wrong replacement...

I need more ideas...

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to