-
Notifications
You must be signed in to change notification settings - Fork 42
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
Multiple fall back input formats for dateconv #138
Comments
Hi, thanks for the report. That's what |
Oh I'm silly, I did not read properly that |
It doesn't appear to operate in a fallback manner, and attempts to apply each input format to every line instead of breaking after the first success. I.e. given this input:
Currently
Ideally I would hope for something like this, where it breaks after the first success.
But this is all heuristic and it seems like the only proper solution to this would be to support fields such as To workaround this I've devised a scheme to ensure titles cannot contain tabs while inserting a tab between the date and the rest of the line. Then |
dateconv -S
is particularly useful when used as a filter for a large amount of input. It would potentially be helpful when dealing with inputs that have a few known formats fordateconv
to try each one in turn until it succeeds.The alternative would be to execute
dateconv
(and perhapsstrptime
) for each line of input.(The ultimate solution would be for
dateconv
to detect the format such as Date.parse from js or dateutils from python)The text was updated successfully, but these errors were encountered: