Version: 2.5.2 (using KDE 3.5.2, Kubuntu Package 4:3.5.2-0ubuntu18.1 dapper) Compiler: Target: i486-linux-gnu OS: Linux (x86_64) release 2.6.18-gg13-mixed64-32 Do Find, fill in text to find as "\n" (without the quotes), check regular expression, and nothing gets matched, even though the document has plenty of newlines. This is on Kate 2.5.2.
That's because kate's find only works on single lines. If you need to match the end of a line, use '$' instead. Otherwise this is a duplicate of bug 36803.
Hello Matthew, Thank you for the reply. I just tried your suggestion, and matching for "$" can't replace the EOL with another character (it would be even nicer if there was a regexp for \n, \r\n, and just "EOL", whatever the file format happens to be). Here's a use case: replace all EOLs with commas (perhaps followed by one space), make some edits, and replace the commas (maybe comma+space) with EOLs. Can Kate do this? Thanks. ---------------------------------------- [bugs.kde.org quoted mail]
Not currently. You want multi-line matching, ala bug 36803. Therefore you should reassign your votes and someone (you?) should close this as a duplicate. Or provide information on how this is not a duplicate. :-)
This is a dupe of a 2002 bug report with 65 votes [1] What puzzles me is that the kate handbook [2] mentions that \n matches a new line. [1] http://bugs.kde.org/show_bug.cgi?id=36803 [2] http://docs.kde.org/stable/en/kdebase/kate/kate.pdf
This is indeed a dupe of bug (feature?) 36803.
On Monday 08 January 2007 22:04, Nick Demou wrote: > What puzzles me is that the kate handbook [2] mentions that \n matches a > new line. Could you link to the relevant section of the HTML version of the docs at docs.kde.org? And, I *did* fix regex search to do this at some point. But there was a regression :( -anders
re-open to re-close as a duplicate of bug 36803
*** This bug has been marked as a duplicate of 36803 ***