[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #15 from Sven Brauch --- I think most of this bug should be fixed in 5.1.80+, at least when editing cpp files. -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 Miki53 changed: What|Removed |Added CC||mickael.serg...@free.fr --

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 Chris changed: What|Removed |Added CC||k...@ontoemail.com -- You are

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 OlafLostViking changed: What|Removed |Added CC|

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #14 from Ian Haber --- the user defined delay works really well for my use case :). i fixed my problems altogether by just turning that timer up. i can now type whatever i want and get autocomplete on it before the

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #13 from Sven Brauch --- Yes, setting the delay to a longer value doesn't update the highlighting faster -- on the contrary, it delays it even more ;) We should probably remove the user-defined delay altogether. I don't

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #12 from Piotr Mierzwinski --- @Sven. Thanks for clear explanation. I hope Milian will find some solution on this annoying issue :/. @Ian. I set it on 4500 ms, but it doesn't help. Still after comment one line

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #11 from Ian Haber --- i just set the background parser delay to a much longer time, so that i can basically modify as much as a want and then stop typing after saving for reparse. it still seems to be slower on

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #10 from Sven Brauch --- When you change the code, a background process is started with a certain delay, which updates the code model (highlighting, ...). _While_ this process is running, the clang-based cpp support

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #9 from Piotr Mierzwinski --- Sorry I'm not sure I got you fully :/. Parser is not slow, only delay(s) make it works slow :/. I understand that parser has to finish its work before I can generate completion list

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #8 from Ian Haber --- is the delay a set time or does it stop delaying as soon as the parser is done? -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #7 from Sven Brauch --- Most of the delay you see is a delay, not the parser being slow. The point is that, right now, as soon as the parser starts you need to wait for it to finish before you can generate a completion

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #6 from Piotr Mierzwinski --- Parser must be run automatically after every change. This is obvious. So I repeat the question: "Why the parser running for kdev-clang is such slow, even on strong hardware?" @Sven.

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #5 from Sven Brauch --- That's exactly the point, by delaying the parser a bit longer we get less cases where completion has to wait for it. The background parser needs to run automatically after every change, that is

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #4 from Ian Haber --- i think the parser is required to update the problems maybe, but it shouldnt have to reparse the whole file just to get the completion for foo->bar(). if i'm adding to the file in such a way

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #3 from Piotr Mierzwinski --- @Ian Haber I think parser working in background is required to properly update the "Problems". I mean update on a regular basis. I wonder why parser running for kdev-clang is such

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 Ian Haber changed: What|Removed |Added CC||master.ha...@gmail.com ---

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 Sven Brauch changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

https://bugs.kde.org/show_bug.cgi?id=371018 Piotr Mierzwinski changed: What|Removed |Added Platform|Other |Archlinux