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
Support change of case on case-insensitive file systems #22
Comments
I think going to the temporal file way is the safest way to do it as you suggested. Adding a flag to ignore all conflicts is quite dangerous in my opinion, taking in to account the safe nets that Thanks for providing this feedback, I will take a look in detail. If you have any other insights about this problem do not hesitate to comment. |
Thanks, I appreciate that it is probably quite hard to work out whether there will be conflicts in this case since it depends so much on the file system. Very happy with |
I have added this feature for Windows/MacOS that lets you rename the same file in case insensitive case-preserving file systems. It checks that the name is the same lowercasing source and target file, but it also checks the file metadata to avoid false positives and unwanted file overwrites. I am very glad you find |
Great, I've tried it out and it looks like it is working perfectly. Thanks! |
On Windows, with a case-insensitive but case-preserving file-system, what's the best way to change the case of a file?
For example, this command produces an error message:
Currently I'm renaming via a temp file name (eg, rename to
.jpg.tmp
, then strip out the.tmp
). Maybe this would work if the conflict detection ignored the source file when checking to see if the target file exists, which is kind of an edge case due to case-insensitivity where the source file won't conflict once it has been renamed.The text was updated successfully, but these errors were encountered: