feat: Support output of checksum in long listing about eza HOT 4 OPEN

Yes, choice between algorithms makes sense.

cksum from coreutils provides some checksums with different algorithms. It also allows to output as hexadecimal string (default), base64-encoded, or raw bytes (only with single files).

❯ eza -1f | xargs cksum -a crc
❯ eza -1f | xargs cksum -a md5
❯ eza -1f | xargs cksum -a md5 --base64

From cksum --help:

DIGEST determines the digest algorithm and default output format:
  sysv      (equivalent to sum -s)
  bsd       (equivalent to sum -r)
  crc       (equivalent to cksum)
  md5       (equivalent to md5sum)
  sha1      (equivalent to sha1sum)
  sha224    (equivalent to sha224sum)
  sha256    (equivalent to sha256sum)
  sha384    (equivalent to sha384sum)
  sha512    (equivalent to sha512sum)
  blake2b   (equivalent to b2sum)
  sm3       (only available through cksum)

from eza.

I quite like this idea but there would have to be a choice between CRC32, MD5, ...

If it's only enabled by a command-line option then checksum calculation would only happen when the option is passed so there would be no slowdown for regular usage.

from eza.

I do not think we would want eza to calculate checksums. It is intentional that it does not read files as it would update the atime of the file. Other utilities already exist to calculate checksums.

from eza.

I agree with @cfxegbert the goal of eza is to not read file contents nor touch at file in any ways.

from eza.