https://bugs.kde.org/show_bug.cgi?id=427481
--- Comment #6 from Igor Kushnir ---
I think there is a way to fix this bug that would actually improve performance
in the normal case when project file sets don't overlap: simply don't remove
duplicates after merging sorted ranges that belong to differ
https://bugs.kde.org/show_bug.cgi?id=427481
--- Comment #5 from Igor Kushnir ---
Git commit 8e0f203ada99acf9e39e4ccd2c8f989ef491eff3 by Igor Kushnir.
Committed on 28/10/2020 at 12:10.
Pushed by igorkushnir into branch 'master'.
ProjectFileDataProvider::projectClosing: match projectPath
The curr
https://bugs.kde.org/show_bug.cgi?id=427481
--- Comment #4 from Igor Kushnir ---
(In reply to Milian Wolff from comment #3)
> I think one way to fix this would be to check if the closed project path
> clashes with one of the other open project paths, and if so, reset the
> provider again. that sh
https://bugs.kde.org/show_bug.cgi?id=427481
--- Comment #3 from Milian Wolff ---
I think one way to fix this would be to check if the closed project path
clashes with one of the other open project paths, and if so, reset the provider
again. that should then re-add any potentially closed files, no
https://bugs.kde.org/show_bug.cgi?id=427481
--- Comment #2 from Igor Kushnir ---
(In reply to Milian Wolff from comment #1)
> If this is important for your workflow, and you really need to have it
> fixed: Adding a vector of projects to every item will have a big performance
> impact if done naiv
https://bugs.kde.org/show_bug.cgi?id=427481
Milian Wolff changed:
What|Removed |Added
Priority|NOR |LO
--- Comment #1 from Milian Wolff ---
Hm, ide
