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.

Sign up for GitHub

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

Jump to bottom

Can't read checksum file if there are any spaces in front of the hash #171

Open
NintendoManiac64 opened this issue Feb 27, 2024 · 0 comments
Open

Can't read checksum file if there are any spaces in front of the hash #171

NintendoManiac64 opened this issue Feb 27, 2024 · 0 comments
Labels
bug

Comments

@NintendoManiac64
Copy link

NintendoManiac64 commented Feb 27, 2024 •
edited

Having an SHA1 checksum file containing the likes of the following examples results in it being unreadable by GtkHash (note that the first example has a leading space!):

 0e8ffcf797749c69525c4190e7f76b5673845f9a *gtkhash-w64-1.5-1-standalone.zip

    0e8ffcf797749c69525c4190e7f76b5673845f9a *gtkhash-w64-1.5-1-standalone.zip

This differs from the likes of HashCheck Shell extension which functions in such a scenario without issue.

The main situation this can occur is when copying text from a webpage or the like where you can commonly end up copying a leading space as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tristanheaven @NintendoManiac64