Day events and --notstarted
Open
type: bug
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 233
- Avg merge
- 1h 44m
- Merged PRs (30d)
- 1
Description
Not sure if this is intended behaviour, but currently I have a day event for today:
❯ khal list
Today, 2021-01-13
test ⟳
and I would expect that by doing:
❯ khal list --notstarted now 30m
would filter out the already-started event, but the output is the same.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the khal list --notstarted now 30m command and compare its handling of day events with the reproduced output. Done means an already-started day event is excluded from the filtered results, with behavior covered by the relevant tests; an open linked pull request already addresses this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100