diff options
| author | Craig Jennings <c@cjennings.net> | 2025-11-17 02:54:02 -0600 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2025-11-17 02:54:02 -0600 |
| commit | 938047cf7447803353565083240531e4c1f076d2 (patch) | |
| tree | fbcc6fcc4b3f8dc8cab76f6909f1cb7b0609d90b /data | |
| parent | 85249d5e9f46150fed3b7fd236708b701326a404 (diff) | |
| download | dotemacs-938047cf7447803353565083240531e4c1f076d2.tar.gz dotemacs-938047cf7447803353565083240531e4c1f076d2.zip | |
fix(calendar-sync): Remove carriage return characters from synced events
Problem:
Google Calendar .ics files use CRLF line endings (RFC 5545 spec), which
resulted in 11,685 ^M (CR) characters appearing in gcal.org, particularly
at the end of org header lines.
Solution:
- Created calendar-sync--normalize-line-endings function to strip all \r
characters from .ics content
- Integrated into calendar-sync--fetch-ics immediately after curl download
- Ensures clean Unix LF-only line endings throughout parsing pipeline
Testing:
- Added comprehensive test suite: test-calendar-sync--normalize-line-endings.el
- 16 tests covering Normal, Boundary, and Error cases
- All 56 existing calendar-sync tests still pass (no regressions)
- Verified: gcal.org now has 0 CR characters (was 11,685)
Files modified:
- modules/calendar-sync.el: Added normalize function, updated fetch function
- tests/test-calendar-sync--normalize-line-endings.el: New comprehensive test suite
Diffstat (limited to 'data')
0 files changed, 0 insertions, 0 deletions