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
Add --dry-run
option.
#3
Comments
Thanks for the issue. This is a good idea, but the collision resolution might make it hard to implement. For example, if the contents of a directory are |
Could you not use a HashSet to store all files (and dirs) in a certain directory and modify the HashSet by removing the key with the old filename with an old name and add a new tilename with the new key while checking that that file does not already exist in the HashSet. For the real file renaming, the old code should be used (as new files can appear while renaming others). |
I think there are cases where the ordering of the files changes what renames happen, and
Yeah, this is a good point. |
Fixed in 2.1.0. I ended up using an in-memory filesystem library. |
It would be nice to have a
--dry-run
or-l
(--list
) option that would just show how files would be renamed, so it is fast to check if-f
will do the job the user wants.The text was updated successfully, but these errors were encountered: