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

Case Sensitivity Consistency across Windows and Linux [Bug (maybe)] #1031

Open
technikker opened this issue Dec 20, 2024 · 1 comment
Open

Comments

@technikker
Copy link

[bug (maybe)]: On Windows, if you rename a folder/file but only change the case (i.e. lower/upper case) so that the original path will still resolve, MEGA will not sync the name change. If you go into the MEGA web UI and do the same thing there, MEGA will sync the name change, even to Windows devices.

I'm not sure if this is fixable, as the Windows API possibly doesn't generate an event upon a case-change rename, but if it does (generate an event), I will consider this a bug.

@mattw-mattw
Copy link

mattw-mattw commented Dec 20, 2024

MEGASync will sync case-only name changes from case insensitive filesystems, but there is an important exception. If the mismatched case files were added in both local and remote when the sync was not running (maybe before the sync was created - and all attributes matching except for filename case), then there is a dilemma - which side is wrong and which should be renamed? Rather than generate a sync conflict for the user to deal with, MEGAsync considers those in sync without an exact match on filename case. If you rename one side or the other to match exactly, then MEGASync will sync case-only name changes for that file going forward. cheers

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