https://bugs.kde.org/show_bug.cgi?id=397343
--- Comment #7 from Ralf Jung ---
But this means it is impossible to have both Kate remember the search state of
Ctrl-F across files, and Ctrl-F work in KWrite.
So either I have to use a non-standard shortcut in Kate (which is a mess, as
Ctrl-F is
https://bugs.kde.org/show_bug.cgi?id=397343
--- Comment #6 from Ahmad Samir ---
The Search & Replace plugin is only available for kate; at the same time both
kate and Kwrite use katepart, so the shortcut you set for the "Find" action is
going to be used in both applications.
The shortcuts can
https://bugs.kde.org/show_bug.cgi?id=397343
--- Comment #5 from Ralf Jung ---
I described above why this is not a great solution: after setting up Ctrl-F to
trigger the search plugin, KWrite has no functioning search any more.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=397343
Ahmad Samir changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=397343
--- Comment #3 from Ralf Jung ---
There is a big problem with this solution: Now Ctrl-F is entirely broken in
KWrite, because I changed the key bindings in Kate.
Is there a way to keep using the normal search in KWrite?
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=397343
--- Comment #2 from Ralf Jung ---
That looks promising, thanks. I don't understand why the default search bar
behaves so strange now. (I think with old kate -- around Kate 4 -- the search
bar still was properly synced between multiple open files.)
--
https://bugs.kde.org/show_bug.cgi?id=397343
--- Comment #1 from Christoph Feck ---
Please enable the 'Search & Replace' plugin. You can also reassign shortcuts to
make Ctrl+F use this as default.
--
You are receiving this mail because:
You are watching all bug changes.
