Don't autosave when replacing in single file

[roblourens]

In #14554 we changed replace to autosave and not open all the files, which makes sense when a replace happens in tons of files. But I think that the old behavior is better for replacing a single entry, or replacing all matches in a single file, and we should keep it.

[sandy081]

I think it will be inconsistent if we automatically save while using one action and not for other actions. Since we show the preview in Search view and also a diff editor for before and after, auto saving while using actions makes sense.

[roblourens]

I think of the two actions differently so I wouldn't mind the inconsistency. When I'm using replace in one file, it's like an edit, and shouldn't autosave when the user has not enabled autosave.

But when replacing across the workspace, I do expect it to just write to all the files in my workspace - I am not "editing" in 300 files simultaneously.

[sandy081]

There are following actions

• Replace all in current workspace
• Replace all in the folder
• Replace all in the file
• Replace a single entry

Except for the last, rest are bulk actions. If we go by edits, only last one should not be autosaved which I think will confuse the user.

[roblourens]

I think that single entry and file go together in that they both just operate on the one file that I'm currently editing, and the others can operate on lots of files. I guess it will be slightly arbitrary if we try to slice that list at all.

[roblourens]

Anyway I'll leave it up to you

[sandy081]

I am kind of convinced to separate between file and multiple files. Will wait for the user feedback to proceed further.

[mgesmundo]

There is a new option to enable/disable the autosave behavior at all?