[kate] [Bug 409642] regex

2019-08-24 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=409642 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[kate] [Bug 409642] regex

2019-07-25 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=409642 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO

[kate] [Bug 409642] regex

2019-07-25 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=409642 --- Comment #5 from Christoph Feck --- New information was added; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 409642] regex

2019-07-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409642 --- Comment #4 from ch-hambur...@freenet.de --- The problem may be minor, though it is illogical that 'Find' and 'Replace' should behave differently. But one or two explanatory lines in the manual, of which you are co-author, would do no harm. :) -- Y

[kate] [Bug 409642] regex

2019-07-09 Thread Dominik Haumann
https://bugs.kde.org/show_bug.cgi?id=409642 --- Comment #3 from Dominik Haumann --- The replace part only supports references like \0, \1, ... Indeed, you should not escape anything else. Maybe we should investigate more, but if you get the correct behavior without \, then this issue is minor.

[kate] [Bug 409642] regex

2019-07-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409642 --- Comment #2 from ch-hambur...@freenet.de --- This is the built-in search. In the 'Find' entry the escape of '{' is a must. In the 'Replace' entry the expected result is obtained by NOT escaping the '{'. But it is not the idea that 'Find' and 'Replac

[kate] [Bug 409642] regex

2019-07-09 Thread Kåre Särs
https://bugs.kde.org/show_bug.cgi?id=409642 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi Resolution|---