Quietly creates backup files (.bak) next to modified files by default
I have been using WinMerge or derivatives for nearly a decade. Every time I install it on a new Windows install, I end up seeing backup files (with names ending in .bak) and wondering where these come from. Depending on circumstances, I sometimes start wondering who is stupid enough to leave such files behind. In any case, I eventually realize it is my PC creating files and wonder which annoying program I forgot to configure so it doesn't create such files. And then, I remember it's WinMerge. Then I go to Options, and figure out after a minute or two I just need to change the option of "Create backup files into:" in the Backup Files section.
Thanks to the option (added following feature requests #581 and #884), 3 minutes suffice to solve the issue on the problematic instance. What is annoying is that I never think about adjusting this right when I install WinMerge, so I always end up polluting folders before I realize what is going on (the first time I installed WinMerge, it took me many weeks to find the culprit). This affects at least WinMerge 2.16.6.
I do not know every user's situation and do not want to recommend a rigid solution. However, I recommend to either:
- change the default behavior so that backup files are not created in the original folder by default, possibly by changing the value of "Create backup files into:" to "Global backup folder"
- or prompt the user asking how to behave, either when installing WinMerge or when about to create a first backup file
In case none of the above is deemed possible/desirable, please at least modify the "Original file's folder" option so that it does not create such files in VCS checkouts (Subversion, Git).
Every time I install it on a new Windows install
Just wondering - why would you not use the Edit -> Options -> Export button to export your old settings and then import them on your new machine / new Windows install ?
Just wondering - why would you not use the Edit -> Options -> Export button to export your old settings and then import them on your new machine / new Windows install ?
Thanks for the suggestion, but quoting myself:
What is annoying is that I never think about adjusting this right when I install WinMerge, so I always end up polluting folders before I realize what is going on (the first time I installed WinMerge, it took me many weeks to find the culprit).
My job is to develop software, not to install Windows. Even if I had a previous WinMerge install easily accessible every time I installed, I doubt transferring would take less time anyway.
Well, as you're a developer - you could automate that via Powershell 😝
A think a default setup should aim to use a clean config as possible.