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

Basing file path in checksum file based on save location is weird. #86

Open
alphaniner opened this issue Apr 29, 2023 · 0 comments
Open

Comments

@alphaniner
Copy link

If I open a directory (eg. test), select some files, run Create Checksum File... and save the checksum file in place, the file paths in the checksum file are as expected:

ab108e300a1483b7fd018bdd15bc6e8df8d0ea01a57bf08508bb77f92a8a1f1a *foo\foobar.txt
0c105a96919a411c86426e54a570bbdb57e6deb312ed0a90e2c91baa3d68e91b *bar.txt

If I save the checksum file in the parent directory, test\ is prepended to all file paths:

ab108e300a1483b7fd018bdd15bc6e8df8d0ea01a57bf08508bb77f92a8a1f1a *test\foo\foobar.txt
0c105a96919a411c86426e54a570bbdb57e6deb312ed0a90e2c91baa3d68e91b *test\bar.txt

If saved to a different drive, the checksum file contains the full paths.

This is unexpected and IMO undesired. If this is intended behaviour please consider making it possible to disable it. Thanks.

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

1 participant