-
Notifications
You must be signed in to change notification settings - Fork 49
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
Detect control files and automatically check for correspondence #165
Comments
Something similar is already possible if you choose "Open..." from the "File" menu and select the example.sha256 file. Or run That is opposite to the way you've described though. |
Why do in 3 clicks what could be done in 1? I'm not asking you to replace the existing function. I'm just asking you to add this automatic feature that I'm sure a lot of people are waiting for! It would also be very useful if this automatic check could be performed in the GtkHash tab in the file properties! This would avoid all the following steps:
All this could be automated with a single click! |
Yes, it's a good idea. I don't think anyone has suggested it before. |
Oh right, I hadn't quite understood. |
Hello,
Would it be possible to implement a function that automatically detects the checksum file associated with a given file, opens it, extracts the string corresponding to the checksum and automatically compares it to the checksum file?
Let me explain:
Suppose I open a "linux.iso" file to calculate its checksum.
Let's imagine that next to it is the file "linux.iso.sha256" or "linux.iso.sha256sum", which is not uncommon, since the two files are often downloaded from the same web page, with the two links next to each other.
It would be very useful to automatically detect whether such a file exists next to the open file. Open it, extract the result (often files contain [result sha256]\t[filename, here it would be "linux.iso"] or the reverse order [linux.iso]\t[result sha256].
In short, adding a condition of this style to the opening of a :
Thank you for everything you can do!
The text was updated successfully, but these errors were encountered: