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

Copy failure involving long paths after compare operation #2100

Open
snovotill opened this issue Nov 10, 2023 · 0 comments
Open

Copy failure involving long paths after compare operation #2100

snovotill opened this issue Nov 10, 2023 · 0 comments

Comments

@snovotill
Copy link

How to duplicate issue "Copy failure involving long paths after compare operation" which affects all versions of WinMerge:

(1) Enable long path support in Windows as follows:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"LongPathsEnabled"=dword:00000001
;"LongPathsEnabled"=dword:00000000

(2) Create a filename or filepath exceeding 260 characters, for example a text file named:
12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901.txt
This must be done via Windows Powershell since the GUI does not support long paths.

(3) Do a file compare between a local drive and a network drive.
The long-named text file will show up in the discrepancies window.

(4) Right-click the file and select to copy it from Left to Right.
The operation fails, likely because WinMerge is calling the deprecated Windows API instead of the currently supported version.

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

No branches or pull requests

2 participants