[WIP] Adding export command to khal CLI #1201
Draft
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.
This PR adds an export command to the command line interface of khal. It takes inspiration from PR #839 but uses the same search interface as the 'edit' command. Searches for a specific UID are therefore possible which addresses issue #892. Similarly, dates and date ranges are possible.
Default is output to
stdout
but output to file is possible via an option. Some examples:Saving instead to file:
This is a WIP as I would like to get some feedback for the approach before going into documentation and tests. I believe that everything discussed in #839 is covered here.
My main concern, however, is handling of repeated events as I am only starting to understand how they work. This approach is not ideal if one specifically wants a given UID: all occurrences of an event are collected before only one is used to retrieve the "raw" ics. From my tests and reading the code, I believe that it does not matter from which of the repeated UIDs I take the raw ics but it would be good to have that confirmed :)
Left to do (from my side):
CHANGELOG.rst
AUTHORS.txt