Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WinMerge incorrectly states "The selected files are identical" #2408

Open
moltenform opened this issue Aug 14, 2024 · 5 comments
Open

WinMerge incorrectly states "The selected files are identical" #2408

moltenform opened this issue Aug 14, 2024 · 5 comments

Comments

@moltenform
Copy link

moltenform commented Aug 14, 2024

Hi all,

WinMerge has unfortunately wasted my time by having me go back and recover deleted files that I thought were safe to delete.

This happened repeatedly: I thought the two files were the same because WinMerge told me "The selected files are identical". And so I deleted one of the supposedly duplicate files.

The files were not duplicates, though. For HTML files, there were important differences in the comments. For some reason differences in comments still show up as the "same".

Firstly, in my opinion WinMerge should show a different message clarifying that the files aren't actually the same. "The selected files are effectively identical due to current comparison settings." vs "The selected files are identical". (For extra credit, a button to press which shows modules/settings have resulted in the files being considered identical).

Secondly, I wouldn't have expected this to occur given my settings. The "plugins enabled" is unchecked. I didn't see anything in settings that would explain what's happening.

image

image

Thirdly, this is open to discussion, but unless this is a bug, in my opinion this is odd behavior to happen by default. I can repro on a vanilla exe of 2.16.42.1.exe, drag/drop the attached files into WinMerge and a message pops up saying they are "the same".

repro.zip

@moltenform
Copy link
Author

Update: I had assumed that this was a malfunctioning plugin treating html files with changed comments as the same. But this seems to happen for any html file.

I can't remember if winmerge stores its settings in localappdata but I'm happy to send over more files in case there's somehow a corrupted state on my machine. Because I'm using the pure .zip from the website I'd assumed the settings were stored alongside the exe.

@sdottaka
Copy link
Member

WinMerge's "Ignore comment differences" option will ignore the differences in comments. Is this option enabled?

I tried comparing the files you attached with the latest version of WinMerge, but the message box "The selected files are identical" did not appear.

WinMerge settings are saved in the registry at HKEY_CURRENT_USER\Software\Thingamahoochie\WinMerge.

After closing WinMerge, could you rename the above "WinMerge" to something else in the registry editor (regedit.exe) and compare the files again with WinMerge?

If the problem does not reoccur, it is likely that some setting is involved, so it would be helpful if you could export the renamed registry data and attach it.

(If the exported text file contains any history data that you do not want others to see, please delete that part.)

image

@moltenform
Copy link
Author

Thank you for the quick reply,

Yes, renaming in the registry does solve the issue.

Before (incorrect):
a3

After (correct):
a3-fixed

I didn't use any advanced features of WinMerge like plugins, so I'm still not sure how the machine got into this state. I haven't run any registry-modifying tools/done anything odd with the registry, and it's a new Windows install from a few months ago. Until recently I used to run winmerge from scoop, until I started using the official x64 binaries from the homepage. The problem occurred on both of them.

state-redacted.reg.zip

@sdottaka
Copy link
Member

I was able to reproduce this issue by importing the configuration data you attached.

When I checked the settings, I found that the file name pattern for image files was empty, as shown below, which caused all files to be treated as image files and text files to not be properly loaded as images, resulting in no differences.

I don't know why the above is empty, but it is not our intention that all files will be compared as images when it is empty, so we will fix this in a future version.

We also hope to fix the behavior when text files are compared as images in a future version.

image

@moltenform
Copy link
Author

moltenform commented Aug 15, 2024

Thank you so much for looking into this!

Yes, this sounds good.

It actually could be my fault that the file name pattern for image files was empty, I remember trying to turn off image comparison and might have left the setting like that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants