Follow-up Comment #2, patch #7963 (project weechat):
b won't work if the checksum is surrounded with _, which I have a distant
memory of seeing before. How about [^0-9A-Z]{1}[0-9A-F]{8}([^0-9A-Z]{1}|$)
?
Except for the kerberos CRC32 variant, CRC32 is the only 32-bit checksum in
libgcrypt, if that counts for popularity. Maybe I should change the string to
"CRC32 OK" and "CRC32 Mismatch"? Then when a mismatch against the wrong
checksum happens the user can make a more informed decision about what to do.
Since this patch just reports the mismatch and doesn't delete anything, it
wouldn't hurt to wait for a feature request before worrying about other
checksums.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/patch/?7963>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
Weechat-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/weechat-dev
