Skip to content
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

uncaught exception with bad command line. #3

Open
cedlemo opened this issue Sep 3, 2017 · 2 comments
Open

uncaught exception with bad command line. #3

cedlemo opened this issue Sep 3, 2017 · 2 comments

Comments

@cedlemo
Copy link

cedlemo commented Sep 3, 2017

@mor1,

When I use a bad argument I have the following error (and no, I did not read the doc before trying sorry)

> ocal 092017
ocal: internal error, uncaught exception:
      Invalid_argument("010920172017 does not match the format %d%b%Y")
@mor1
Copy link
Owner

mor1 commented Sep 3, 2017

Hm, yes. That's not the best error message is it? :)

The format should be MMMYYYY where MMM is Jan, Feb, etc, and YYYY is 2017, 2018 etc.

But I'll leave this issue open to remind me to do something about the error handling for the next release. I won't have time to get to it for several weeks though I'm afraid. (Term starting means the day job is about to reassert itself.)

@cedlemo
Copy link
Author

cedlemo commented Sep 3, 2017

ok, no problem, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants