https://bugs.kde.org/show_bug.cgi?id=444883
--- Comment #4 from Sven Brauch <m...@svenbrauch.de> --- Hi Waqar, thanks for having a look at this. The problem is not (only) that it is slow in KDevelop, the problem is also that it now misbehaves. Try it out with a somewhat large project; the re-querying will somehow forget the search keyword on updating the list, leaving the first entry to be completed always, unless another character is typed again. Additionally, cancellation doesn't work properly; e.g. typing "foo();<Enter>" will very easily leave you with some nonsense completion (e.g. "foo();__func__") added at the end of the line, I guess because the updated results only become available after the completion isn't relevant any more. I think I already mentioned in one of the related merge requests that any changes to the completion list needs to be very carefully tested in KDevelop, because it is basically the only consumer for a large part of its functionality. Checking that things still work in Kate simply isn't enough. As it is now, the changes done in KTextEditor leave the completion widget's most important downstream (KDevelop) in a pretty broken state, with (to me) no clear path to fixing it. Best, Sven -- You are receiving this mail because: You are watching all bug changes.
