mirror of
https://github.com/SabreTools/NDecrypt.git
synced 2026-02-04 05:35:53 +00:00
Wrong usage for --hash flag is displayed after decryption #10
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mariomadproductions on GitHub (Sep 27, 2022).
Originally assigned to: @mnadareski on GitHub.
If you use the --hash / -h flag but don't provide a path afterwards, the program only tells you of your error after the decryption/encryption is completed. And by then, the program has already read the file, so calculating the hash would take double the time. Only a minor thing, but still.
@mnadareski commented on GitHub (Sep 27, 2022):
Please provide an example of your commandline. I have a feeling that you're adding the flags after the path you're decrypting, not before, as the help and readme both indicate.
@mariomadproductions commented on GitHub (Sep 28, 2022):
Yeah, I think I provided it at the end.
@mnadareski commented on GitHub (Sep 28, 2022):
Proper usage, as copied from the README:
NDecrypt.exe <operation> [flags] <path> ...@mariomadproductions commented on GitHub (Sep 28, 2022):
Usually command line programs allow variable orders, but okay np.