Fix crash on unparseable datetime range in khal new -i - #1483
Open
John-Wassilak wants to merge 2 commits into
Open
Fix crash on unparseable datetime range in khal new -i#1483John-Wassilak wants to merge 2 commits into
khal new -i#1483John-Wassilak wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #789.
khal new -i's datetime-range prompt crashed and discarded the whole event on an unparseable range instead of re-prompting, like the other fields in the same loop already do. Also improves the parse error to show a formatted example using the configureddatetimeformat.