Frédéric Mahé

Earlier this year, I tried to write a manpage in markdown format. It is quite promising, but also very time consuming. If I find time to do it (summer 2024?),...

Revisiting this potential new feature, I have a few questions: How to deal with data streams (pipes or process substitutions)? ```sh vsearch --derep_fulllength "${INPUT}" vsearch \ --derep_fulllength "${INPUT}" \ --minseqlength...

No problem, I am here for the long run. Thanks a lot for that new feature!

tests added https://github.com/frederic-mahe/vsearch-tests/commit/8b6f8ce07a15e342085da117e8db923f00a6fd49 Without looking at the code, and given the fact that `--xlength` and `--lengthout` can be used at the same time, I am right to assume that `--xlength`...

I've updated the manpage to indicate that `--xlength` acts on input and can be combined with `--lengthout` (see https://github.com/torognes/vsearch/commit/53b94e527b684072877a153f6475f23c0db973ba) Finally closing that issue old issue :-)

issue fully tested in our test suite (see https://github.com/frederic-mahe/vsearch-tests/commit/8b6f8ce07a15e342085da117e8db923f00a6fd49)

This is great! I think I'll finish writing additional black-box tests for the `--derep_fulllength`, then I'll try to write more tests for this new chimera detection command. Some tests could...

@nbokulich and @torognes I was not able to reproduce this bug (i.e., unexpected number of columns in `blast6out` output). Using the same vsearch release, the same command line arguments, and...

I suggest to close the issue for now. `PotentialFuture` tag allows us to find and revisit that issue if need be.

Closing for now. We can always revisit in the future (use the tag PotentialFuture to select these items)