Replies: 3 comments 1 reply
-
Hi @feldroop, not sure if I understood you correctly. Do you think
is confusing and it should be
? |
Beta Was this translation helpful? Give feedback.
-
Yes, that's pretty much what I think. I feel like people who use command line tools are generally not interested in the version of the command line parser their tool uses. Especially not biologists who use bioinformatics tools. Most people will just ignore it, but it's still unnecessary noise. In the worst case, desperate users, who struggle with debugging their workflows, might think: "What is this sharg thing in the help menu? Do I have the wrong version? Maybe that's why it doesn't work?". Most likely sharg is not the reason for their problems and it's not like they can change the sharg version independently of the tool version either. I would argue that it's an unnecessary leakage of an implementation detail. |
Beta Was this translation helpful? Give feedback.
-
It's not so uncommon:
SeqAn2 does it too:
We even print the seqan3 version if it's used
Another thing is visibility (of the sharg lib), and IMO |
Beta Was this translation helpful? Give feedback.
-
I feel like printing the sharg version into the help menu does not really help the user of an application. It might actually be confusing.
Beta Was this translation helpful? Give feedback.
All reactions