- Visit a folder that includes a subfolder, a file with a size >= advanced setting
max_md5_file_size(5 MB for me), and some small but non-empty files. - Put the file display in details mode (with columns).
- Make sure nothing is selected.
- Use quick key
>to run the commandGetSizes HASH=md5, or with another hash algorithm that didn't already show a column for you and that you definitely didn't generate hashes for in the past for these files.- All files including the large file now show hashes.
- Visit the subfolder and go back up.
- The large file now shows "<file too large>" instead of a hash, while the other files still show their hashes. This seems to be expected, because, as I understand it, hashes for smaller files are calculated when visiting the folder, if a hash column is shown, and
max_md5_file_sizeprevents this recalculation for the large file.
- The large file now shows "<file too large>" instead of a hash, while the other files still show their hashes. This seems to be expected, because, as I understand it, hashes for smaller files are calculated when visiting the folder, if a hash column is shown, and
- Bug (?): When running the command again without a selection, "<file too large>" doesn't disappear.
- Another bug: Only when running the command again while the large file is the first selected file does it show its hash again. It doesn't work if the a file above it is also selected.
BTW: Since GetSizes HASH=sha1, e.g., also updates the hashes in visible columns for other hash algorithms, GetSizes HASH without a hash algorithm could be useful to just update missing (or recalculate all?) hashes in currently visible columns.