Creating new event with start and end time results in an "All Day" event with the end time and time zone in the Title
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 233
- Avg merge
- 1h 44m
- Merged PRs (30d)
- 1
Description
Describe the bug
This:
khal new 30/06/2025 09:30 10:30 Europe/Helsinki Another Event :: with Alice and Bob
Produces an event like this:
Title: 10:30 Europe/Helsinki Another Event
Date: 30/06/2025
Calendar: personal
with Alice and Bob
To Reproduce
Run
khal new 30/06/2025 09:30 10:30 Europe/Helsinki Another Event :: with Alice and Bob
and check with khal interactive
Expected behavior
Expect the event not to be "All Day" and be in the right time zome and has a start and end
Title: Another Event
Date: 30/06/2025 9:30 - 30/06/2025 10:30
Calendar: personal
with Alice and Bob
OS, version, khal version and how you installed it:
- The output of khal --version: khal, version 0.13.0
- Installation method: OS repo
- python version: Python 3.12.10
- OS: NixOS 25.05.20250515.e06158e (Warbler)
- Your khal config file
$ cat ~/.config/khal/config
[default]
default_calendar = personal
[calendars]
[[calendars]]
path = ~/.local/share/calendars/*
type = discover
[locale]
timeformat = %H:%M
dateformat = %d/%m/%Y
$
- The versions of your other python packages: pip is not installed
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 by running the reported khal new 30/06/2025 09:30 10:30 Europe/Helsinki Another Event :: with Alice and Bob command, then inspect the result with khal interactive. Trace how the command parses the end time and time zone, and consider the issue done when the event is timed, uses Europe/Helsinki, retains Another Event as its title, and shows the expected start and end.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100