| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The surface reading this has to stay correct while Emacs is down, and
emacsclient is exactly the thing that cannot. So the writer is a batch
Emacs and a user timer runs it every five minutes.
- scripts/agenda-render-cache writes the cache from a batch Emacs. It
resolves the agenda file list through the config's own resolver rather
than restating it, so adding a calendar source stays a one-place change.
- The timer uses OnCalendar so Persistent actually applies. On a monotonic
schedule it is silently ignored, and a machine that slept would come back
to a stale file with nothing to trigger a catch-up.
- The window is now three days, yesterday through tomorrow. A consumer
drawing a rolling window centred on now has nothing to draw for the part
of its span outside today, which late in the evening is half the surface.
The keyword list moved to user-constants, where a batch Emacs can reach it
without this config's package dependencies. Without it org did not
recognise DOING or VERIFY, so it stopped parsing those headlines as tasks
at all: the keyword and priority cookie stayed glued to the front of every
title and each row reported no keyword and not-done. The file parsed
cleanly and was wrong, which is the failure worth guarding.
The bats tests run against a fixture and this checkout, not the machine's
real agenda and installed config. Asserting over live data let the same
suite pass on a day that happened to have no keyworded entries.
|
|
|
The surface that reads this went live, and it reads a different shape than
the canonical profile emits.
- cj/agenda-render-json adds s and e in epoch milliseconds, plus t for the
title. The canonical fields ride along, so one file serves both readers.
- Every row gets an end it can be drawn with. An all-day entry spans its
day. A point event has zero width. The canonical profile still reports
null there, which is faithful to the source but not a width.
- cj/agenda-render-cache-update writes today to the XDG cache path.
Input stays epoch seconds on both profiles. Only the output converts, and
the guards that catch a milliseconds-for-seconds caller still apply.
Nothing schedules the cache write yet, so the file is only as fresh as its
last call. Picking a refresh mechanism is its own decision.
|
