You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I copy/paste text into WinMerge, then refresh to compare and then double click the row with the difference, the difference is highlighted incorrectly.
Note that the last zero on the "smallint" line is highlighted. I think WinMerge is thinking the the zero and tab from the left side doesn't exist on the right side so it highlights it and the last zero from the right side is highlighted because it doesn't exist on the left side.
This might be OK but if I compare the two text files in WinMerge (I just realized my shortcut points to 32-bit v2.14.0) using Windows Explorer to highlight both files and then choosing Send To > WinMerge, then it compares and highlights the difference differently.
This does not happen with v2.16.4.0.
Note that it highlights the "1" from both sides.
I expect the difference (regardless of version) to show the "0 1" and "1 0".
If I load the files in a brand new WinMerge session using the "Select Files or Folders" tab, then the compare results are similar to the first method that I mentioned:
I'm using v2.16.4.0 on Windows 10 64 bit. While writing the bug, I just realized the shortcut in the SendTo folder points to 32-bit v2.14.0.
The text was updated successfully, but these errors were encountered:
This looks like your comparison options between the two versions are different.
That could be true since one appears to be the 64-bit version, while the other is the 32-bit version.
When I copy/paste text into WinMerge, then refresh to compare and then double click the row with the difference, the difference is highlighted incorrectly.
Note that the last zero on the "smallint" line is highlighted. I think WinMerge is thinking the the zero and tab from the left side doesn't exist on the right side so it highlights it and the last zero from the right side is highlighted because it doesn't exist on the left side.
This might be OK but if I compare the two text files in WinMerge (I just realized my shortcut points to 32-bit v2.14.0) using Windows Explorer to highlight both files and then choosing Send To > WinMerge, then it compares and highlights the difference differently.

This does not happen with v2.16.4.0.
Note that it highlights the "1" from both sides.
I expect the difference (regardless of version) to show the "0 1" and "1 0".
I attached the two text files for sample testing.
winmerge_bug2.txt
winmerge_bug1.txt
If I load the files in a brand new WinMerge session using the "Select Files or Folders" tab, then the compare results are similar to the first method that I mentioned:

I'm using v2.16.4.0 on Windows 10 64 bit. While writing the bug, I just realized the shortcut in the SendTo folder points to 32-bit v2.14.0.
The text was updated successfully, but these errors were encountered: