Bug 384899 - find/replace key persistence causes find/replace toolview "trolling"
Summary: find/replace key persistence causes find/replace toolview "trolling"
Status: RESOLVED FIXED
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: grepview (show other bugs)
Version: git master
Platform: Compiled Sources All
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-20 21:04 UTC by RJVB
Modified: 2017-09-30 19:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
untrolling patch (612 bytes, patch)
2017-09-22 19:47 UTC, RJVB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description RJVB 2017-09-20 21:04:09 UTC
The find/replace plugin apparently started saving its last/current search key among the project settings in the 5.2 branch.

I think this has the result that the corresponding toolview now has a habit of opening unexpectedly and relaunching the last search. For me that happens when I load the session but also when I start the patchreview toolview to view a diff or to commit a change.

Both are annoying and undesirable (and potentially costly).
Comment 1 Kevin Funk 2017-09-21 07:09:42 UTC
I noticed that, too. +1.
Comment 2 Kevin Funk 2017-09-21 07:11:23 UTC
Relevant patch: 
  https://phabricator.kde.org/D6262
Comment 3 Kevin Funk 2017-09-21 07:13:16 UTC
Feature request was here:
  https://bugs.kde.org/show_bug.cgi?id=380864

@René: Could you raise a discussion on the mailing list? I also think that new feature is unfortunate.
Comment 4 Christoph Roick 2017-09-22 18:52:30 UTC
Actually I didn't think about different views, so I admit this can get annoying. What do you think about just storing the search parameters and letting the user decide when to click the "Refresh" button?
Comment 5 RJVB 2017-09-22 19:47:01 UTC
Created attachment 107957 [details]
untrolling patch

I have been meaning to rewind some of your changes one by one to see what could be a good compromise. It seems this patch already removes the really annoying things. I wasn't expecting it would solve the grep toolview usurping the patchreview toolview, but apparently it does.

Yeah, history is fine, but only the user knows if and when it should be replayed.
Comment 6 Christoph Roick 2017-09-22 22:24:54 UTC
It should stay silent with the new patch:
  https://phabricator.kde.org/D7945
It still keeps the old search parameters accessible.
Comment 7 Kevin Funk 2017-09-24 20:13:13 UTC
Git commit e9726dc8f578d8e0a6fc23f9ba7ffc9ef29f0d5d by Kevin Funk, on behalf of Christoph Roick.
Committed on 24/09/2017 at 20:07.
Pushed by kfunk into branch '5.2'.

Revert automatic grep job execution from Find in Files history

Summary:
- raise of output view is suppressed for jobs from history
- only search parameters are displayed, actual search can be
  redone with "Refresh"
- population of list is still deferred until all projects
  are loaded to ensure correct display of search description

Test Plan:
- on restart no search is performed, but can be triggered by "Refresh"
- output view stays closed on startup

Reviewers: #kdevelop, brauch

Reviewed By: #kdevelop, brauch

Subscribers: brauch, kdevelop-devel

Differential Revision: https://phabricator.kde.org/D7945

(cherry picked from commit b99043910feaf9046d76bfe2cc8fabdd2e68e8b9)

M  +29   -17   plugins/grepview/grepdialog.cpp
M  +2    -0    plugins/grepview/grepjob.h
M  +4    -6    plugins/grepview/grepoutputview.cpp

https://commits.kde.org/kdevelop/e9726dc8f578d8e0a6fc23f9ba7ffc9ef29f0d5d