lsseq didn't gracefully handle the case when a sequence has duplicate frame numbers, eg. two frame 5's, but only different in terms of the padding of the frame number.
This is clearly a problem that the user created by having an extra file (likely unintentional), however when lsseq was attempting to list frames with bad-padding (i.e files that had numbers that didn't match the padding of the sequence), the code wasn't properly accounting for the possibility of two entries with the same frame number in an internal database, and it was causing unintended consequences when trying to come up with the list of badly padded frames. This has been fixed,
NOTE: that this bug ONLY affected the listing of badly padded frames, all other output of lsseq was correct.
Also "warnings" are now issued if/when such duplicate files are found.
Therefore --showBadPadding correctly lists all badly padded frames.
Also added --silent and --quiet also, to suppress printing of warning messages. Previously the only warning printed was if a broken soft link was present.
Furthermore, changed names of three env vars, that the user can use to adjust the list of image-extensions, or cache-extensions etc, from OIC_* to LSSEQ_* - however the code is quiet about it, but still supports the use of the old names for backward compatibility.