Version: unspecified (using KDE 4.5.0) OS: Linux In KDE 4.4, I used to be able to search for a term by selecting it, pressing Ctrl-F, then pressing Enter. Now, however, pressing Enter causes the search term to be replaced with something else (maybe from a previous search?). Reproducible: Always Steps to Reproduce: Select a word. Press Ctrl-F. Press Enter. Actual Results: Kate searches for some unrelated term. Expected Results: Kate should search for the term I selected.
I have the same problem in KDevelop from trunk (kdelibs, kdesdk ... also from trunk) though I can't always reproduce it. The way it looks like here is I search for a certain term A and press next. Suddenly the search term changes to B and the find is also B, pressing again changes it to C ...
I also had this just now. To reproduce: asdf foobar yxcv 1) search for asd 2) search for foo 3) search for yxc 4) ctrl + f -> select some item from the history (e.g. asd again) 6) f3
Fixed in git, need to be merged into SVN and backported into 4.6 branch commit 9ba4d7adbe6c5350cc1f885b878ff13d5b28c383 Author: Milian Wolff <mail@milianw.de> Date: Mon Dec 20 13:55:56 2010 +0100 fix regression introduced in f52c93919a158decd3399d0893efa49e57547009 properly set the current index in addCurrentTextToHistory BUG: 248305
SVN commit 1209887 by cullmann: mwolff: fix regression introduced in f52c93919a158decd3399d0893efa49e57547009 properly set the current index in addCurrentTextToHistory BUG: 248305 M +3 -8 search/katesearchbar.cpp M +0 -1 search/katesearchbar.h M +6 -0 tests/searchbar_test.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1209887
*** Bug 261655 has been marked as a duplicate of this bug. ***
Does this also fix the same problem that arises when you do press Ctrl+F, enter word and press enter?
*** Bug 262465 has been marked as a duplicate of this bug. ***