https://bugs.kde.org/show_bug.cgi?id=456767
--- Comment #14 from Igor Kushnir <igor...@gmail.com> --- OK, now I see how this happens: GrepOutputView() reads LastSettings KConfig entry, then creates a GrepDialog and starts historySearch() to "rerun the grep jobs with settings from the history" (why???). GrepDialog::historySearch() connects GrepDialog::checkProjectsOpened to IProjectController::projectOpened and invokes nextHistory(true) asynchronously, which calls GrepDialog::startSearch(). This invocation occurs when some nested event loop is entered - from Kasten::JobManager::executeJob() in the backtrace of the first comment in this bug. Apparently nextHistory() is inlined and thus missing from the backtraces. https://commits.kde.org/kdevelop/42eb6bb62c28923e5f6f4ff0cee3e8e6ee07bd2e has implemented this feature. I'll ask the author of that commit why the last search has to be rerun, as opposed to simply restoring the find-in-files history as requested by the linked bug reports, in a GitLab comment. -- You are receiving this mail because: You are watching all bug changes.
