Repeated tasks on the calendar with --once should only show next occurance, not all of them
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 233
- Avg merge
- 1h 44m
- Merged PRs (30d)
- 1
Description
Hi, I am generating ics file from org-mode and importing into khal with
khal import -a todo --batch ~/.todo.ics
and everything works great.
Now I have reoccurring task happening every week, example from ics file would be
BEGIN:VEVENT
DTSTAMP:20230410T175402Z
UID:TS1-af74116d-3ee3-42aa-b187-02be8451b958
DTSTART;VALUE=DATE:20230417
DTEND;VALUE=DATE:20230418
RRULE:FREQ=WEEKLY;INTERVAL=1
SUMMARY:Here is some repeating task example
DESCRIPTION:Yes, description too.
CATEGORIES:todo
END:VEVENT
and khal calendar --once today 30d correctly shows task once in the 'at' list on the right, but calendar itself highlights all Mondays in the future.
Expected behavior: with --once and repeated tasks, khal should only highlight next date on the calendar, not all repeated dates in the future.
I can snap screenshot if needed but this is easy to test and replicate. Anything I can help with just let me know.
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
Reproduce the issue with the shown recurring VEVENT and khal calendar --once today 30d; start by tracing the calendar command's --once handling and recurring-event display path. Done means the calendar highlights only the next occurrence while the command retains its expected single entry.
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
- Clearly specified
- Newbie friendliness
- 35/100