-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running ocrd
or a processor without arguments should output --help
AND return 1
#1209
Comments
I don't think so. Both behaviours are well documented. Processors adhere to the OCR-D CLI specification, and |
@bertsky, thank you for pointing to the OCR-D CLI specification. Where is it documented that running |
That's click's default (because traditionally that's how multi-task CLI behave).
I totally disagree. First of all, this would break existing usage without even a reason. Second, there is simply no need for "consistency" with OCR-D processors, as this is a different kind of CLI, as I have already pointed out. |
Please give more evidence for that statement. I just tried
Do you have a real-life example of this? |
Most OCR-D processors return 1 when they are called without any argument, but
ocrd
from core is an exception which returns 0. Should that be changed?Originally posted by @stweil in OCR-D/ocrd_froc#13 (comment)
The text was updated successfully, but these errors were encountered: