ZipSeq: splits are erroneously detected as re-zippable when they are not #3
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I don't deal with splits often enough but this warrants investigation
This was a fluke on the network drive, possibly a thumbs.db issue? So I need to double check if thumbs.db is ignored by zipseq universally.