dotemacs/tests/test-calendar-sync--event-to-org.el, branch mainMy Emacs configuration
https://git.cjennings.net/dotemacs/atom?h=main2026-05-04T04:51:59+00:00fix: sanitize calendar event headings and property values2026-05-04T04:51:59+00:00Craig Jenningsc@cjennings.net2026-05-04T04:51:59+00:00urn:sha1:f610c2fef97381c7ecfc9dca0a0e1a39a16abe18
`calendar-sync--event-to-org` already cleaned the description body via `calendar-sync--sanitize-org-body`, but the event summary went into the heading line and the location, organizer, status, and URL went into the property drawer without sanitization. Any of those fields containing newlines could create extra Org headings, close the property drawer early with a stray `:END:`, or inject property-looking lines that the agenda would then parse as real properties.
I added two helpers. `calendar-sync--sanitize-org-property-value` trims the input and collapses any run of whitespace or newlines into a single space. `calendar-sync--sanitize-org-heading` composes that over the existing body sanitizer so `*` sequences also become `-`. The event-to-org function now routes the summary through the heading sanitizer and each property value through the property sanitizer.
I added regression tests across two files. `test-calendar-sync--sanitize-org-body.el` gets 4 new tests for the two helpers, covering newline flattening, leading-star replacement, structural-character flattening, and whitespace collapse. `test-calendar-sync--event-to-org.el` gets 2 new integration tests. A summary containing `\n** Hidden task` produces a single `* ` heading with the body inlined. A location containing `\n:END:\n* Not a real heading` collapses to a single property line with no extra `:END:` or heading injected.
515 calendar-sync tests pass together.
fix(calendar-sync): sanitize description text to prevent org heading corruption2026-02-06T16:15:08+00:00Craig Jenningsc@cjennings.net2026-02-06T16:15:08+00:00urn:sha1:6f2a854378b3b14d58cf4e567a3b1c5174484c12
Event descriptions containing lines starting with * were being interpreted
as org headings, breaking file structure. Replace leading asterisks with
dashes before writing descriptions.
fix(calendar-sync): fix heading order, continuation lines, and exception text cleaning2026-02-05T22:10:09+00:00Craig Jenningsc@cjennings.net2026-02-05T22:10:09+00:00urn:sha1:1039eca8800959a6a889f3b6d94a4742b794160c
Three bugs found during manual verification of calendar sync output:
1. Heading/timestamp order reversed in event-to-org — nreverse pattern
put timestamp before the org heading. Swap initial list order.
2. get-property continuation line regex broken — the ^ anchor in
"^\n[ \t]" prevented matching at the correct position, truncating
long DESCRIPTION values at the first ICS line fold. Remove anchor,
add explicit position check (matching get-all-property-lines pattern).
3. collect-recurrence-exceptions didn't clean text — exception instances
got raw ICS text (literal \n, HTML tags) replacing the cleaned base
event text. Wrap summary/description/location in clean-text.
feat(calendar-sync): add event details — attendees, organizer, status, URL2026-02-05T21:13:57+00:00Craig Jenningsc@cjennings.net2026-02-05T21:13:57+00:00urn:sha1:d226f80a376c97a6adbcbc800be647cb69f0b50b
Add ICS text unescaping (RFC 5545), HTML stripping, and new fields
(attendees/status, organizer, meeting URL) to calendar-sync.el.
event-to-org now outputs org property drawers. 88 new tests across
10 test files, 146/146 pass. Also fix pre-existing test require
order and keymap guard issues.