Created attachment 123179 [details]
screenshot 1

SUMMARY
I have now seen 2 cases where I edit a file, close it without saving the changes (because to be discarde) and KDevelop then keeps bugging me about unsaved changes in that file.
See the screenshots.


STEPS TO REPRODUCE (tentative, this is what I did just now when it happened again)
1. start patchreview mode to review saved changes
2. change something more in one of the files
3. close that file without saving the new changes
4. exit patchreview mode (NB: I may have skipped step 3, knowing the file would be closed in this step 4)
5. re-open the patchreview mode

OBSERVED RESULT
I don't think I was asked to save when I closed the file. When I restarted patchreview mode I got the "there are unsaved changes" dialog (screenshot 1) which I dismissed by clicking "No". The patchreview mode then warned me about an improperly saved file (screenshot 2).

EXPECTED RESULT
None of the above. There should be no keeping track of unsaved changes in files that are not open (or else there should be a very explicit option to *opt in* to such behaviour).

SOFTWARE/OS VERSIONS
KDevelop 5.4/head
KDE Frameworks Version: 5.60.0
Qt Version: 5.9.8

NB: I haven't been able to use the 5.4 version enough on Mac; I expect this is not platform-related.