I marked the new version of these two commands as `v3.0.0`, which indicates a MAJOR version change from the prior v2.3.0, suggesting an incompatible API change.
This update ALMOST qualified for a `v2.4.0`, as the non-backward-compatible change was only to change the default of the `--delimiter` OPTION from `comma` to `space`.
I felt this change was important because being a shell command, and outputting space delimited results is far more useful when back-quoting or expanding the results into a shell-variable etc.
Every time I used the previous version in a shell script, I opted for `--delimiter space` to override the default `comma`. I can't imagine that anyone is relying on the output being comma separated, but if so, apologies, you are going to have to modify your scripts that use these commands if so. Unfortunately `space` is the right choice for the default delimiter for a shell command.
Note that any scripts that had `--delimiter space` in use before will still work exactly the same now, so I think this change is quite safe.
The two commands have been split into two separate files now too, so as to allow us to print out the program-names properly in usage, and error or warning messages. Using argv[0] doesn't work on some revision control systems, which messes up warning and error messages - anyway, no longer an issue with this release.
Also, removed the option to `--reverse` the lists produced in `condensseq` because it didn't make sense given that the `FRAME-RANGEs` produced didn't also get reversed. That is not a feature supported by the underlying library `seqLister` that is at the heart of these two commands. I consider removing `--reverse` from `condensseq` a bug-fix, mind you a design-bug-fix.
Lastly, added in some code to report on any bad FRAME-RANGEs being passed to the commands, and either exit with error (and error code `1`), or produce a warning, with the ability to be `--silent` too.