Summary: | Kate forgets search results if multiple search tabs are active | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Volkan <volkangezer> |
Component: | search | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kare.sars |
Priority: | NOR | ||
Version: | 3.12.97 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kate/cc47ba960bbe296bccbccbf6722aa434a348e908 | Version Fixed In: | 3.13 (KDE 4.13) |
Sentry Crash Report: |
Description
Volkan
2014-04-05 13:43:44 UTC
Hi, thanks for the report. It seems that the plugin is doing a search in current file when the tab is changed, which it should not.. I'll have a look. Git commit 44ce3d0cb87f640348f8f657ac1c3b51273df87b by Kåre Särs. Committed on 05/04/2014 at 20:15. Pushed by sars into branch 'master'. S&R: Do not trigger searchWhileTyping on result tab change FIXED-IN: 3.13 (KDE 4.13) M +6 -0 addons/kate/search/plugin_search.cpp http://commits.kde.org/kate/44ce3d0cb87f640348f8f657ac1c3b51273df87b Git commit cc2eb4a26dc27eee20b1b8376065a00be90fac2e by Kåre Särs. Committed on 05/04/2014 at 20:15. Pushed by sars into branch 'KDE/4.13'. S&R: Do not trigger searchWhileTyping on result tab change FIXED-IN: 3.13 (KDE 4.13) M +6 -0 addons/kate/search/plugin_search.cpp http://commits.kde.org/kate/cc2eb4a26dc27eee20b1b8376065a00be90fac2e Git commit cc47ba960bbe296bccbccbf6722aa434a348e908 by Kåre Särs. Committed on 05/04/2014 at 20:33. Pushed by sars into branch 'frameworks'. S&R: Do not trigger searchWhileTyping on result tab change FIXED-IN: 3.13 (KDE 4.13) M +6 -0 addons/search/plugin_search.cpp http://commits.kde.org/kate/cc47ba960bbe296bccbccbf6722aa434a348e908 I still experience this in KDE 4.14.1 Hmm... I can not reproduce it.... Not with git nor with Kubuntu packages KDE 4.13.0 Kate 3.13.0 Are you sure you got Kate updated? If you did I might need a more detailed steps to reproduce.... It says Kate version 3.14.1 Ok, yes you are right. It works. False alarm :). The issue is now different, but I will open a new ticket for it. |