aboutsummaryrefslogtreecommitdiffstats
path: root/CHANGELOG.md
diff options
context:
space:
mode:
authorDanilo M. <danix@danix.xyz>2026-09-24 17:38:52 +0200
committerDanilo M. <danix@danix.xyz>2026-09-24 17:38:52 +0200
commitcfd96a07b5b14abe1585f0edf68cd0b9c8975463 (patch)
tree2e8c613af723f5b3a60e9a345ac29c85ea06f837 /CHANGELOG.md
parent516b2daaeab00bb4d4c28055a434dc5ee53aeb60 (diff)
downloadqtmaildir-cfd96a07b5b14abe1585f0edf68cd0b9c8975463.tar.gz
qtmaildir-cfd96a07b5b14abe1585f0edf68cd0b9c8975463.zip
docs: document the calendar, translate it, file its follow-ups
Give RepeatRule its own Q_DECLARE_TR_FUNCTIONS context so lupdate extracts describe() and the ordinal words, mirroring the array's QT_TRANSLATE_NOOP; without it lupdate warned and RepeatRule/last was never extractable.
Diffstat (limited to 'CHANGELOG.md')
-rw-r--r--CHANGELOG.md25
1 files changed, 25 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md
index cb58e2c..a1b6b92 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -13,12 +13,37 @@ point at which they are stable.
### Added
+- **A calendar window.** **View > Calendar** opens a month grid, with an Agenda
+ view one toggle away and a side pane that shows the selected event and turns
+ into the edit form. Events can be created, edited and deleted, each undoable
+ with `Ctrl+Z`, and the pane says when an event was organised by someone else,
+ which is read-only. It reads and writes the vdirsyncer vdir directly, so khal
+ is not needed; names and colours come from the collections' own `displayname`
+ and `color` files. The feature is off until `calendars_dir` names the vdir.
- **Contact completion.** Point `contacts_dir` under `[general]` at a directory
of vCards, vdirsyncer's `~/.local/share/vdirsyncer/contacts/` being the usual
one, and the composer's To, Cc and Bcc fields and the query bar's `from:` and
`to:` complete against it. The store is read-only and loaded once at startup;
omit the key and the feature is off.
+### Upgrading
+
+**The calendar is off until `calendars_dir` is set.** No existing config key
+changes meaning and nothing breaks by doing nothing: without the key the
+calendar action is simply absent and no vdir is read. To turn it on, point it
+at your vdir root and, if new events should land in one collection rather than
+the first, name that collection's directory in `default_calendar`.
+
+**A vdirsyncer cron line should take the same lock the calendar uses.** The
+default `calendar_sync_command` is prefixed with
+`flock -w 60 /tmp/vdirsyncer.lock`, so a save in the calendar and a cron run do
+not sync at once. Add the same prefix to your cron line and append
+`&& vdirsyncer metasync` to keep the collections' names and colours current:
+
+```cron
+*/30 * * * * flock -w 60 /tmp/vdirsyncer.lock vdirsyncer sync calendars && vdirsyncer metasync
+```
+
## [0.29.0] - 2026-09-14
Spam is now a folder you can act on: Mark spam moves the file into a