TODO items, logging, repeaters and priorities

Try: on "Cycle me", press cit twice. Expect: the heading reads NEXT Cycle me (first TODO, then NEXT).

Try: press ciT twice. Expect: back to Cycle me with no keyword.

Try: press ciT once more. Expect: FIXED Cycle me (going backwards from "no keyword" wraps to the last keyword), with a CLOSED: [...] line and a line - State "FIXED" from "" [2026-09-28 Mon 15:08] under it ("" because there was no previous keyword).

Try: on "Water the office plants", press <C-c><C-t> then n. Expect: NEXT Water the office plants.

Try: press <C-c><C-t> then d. Expect: DONE Water the office plants, followed by CLOSED: [2026-09-28 Mon 15:08] and - State "DONE" from "NEXT" [2026-09-28 Mon 15:08].

Try: press <C-c><C-t> then <Space>. Expect: the keyword is gone and so is the CLOSED: line (the log line stays: it is history).

<C-c><C-t> takes a count like Emacs' prefix argument. A plain number N jumps to the N-th keyword of the file (in the order shown above), but 4, 16 and 64 mean C-u, C-u C-u and C-u C-u C-u:

When no keyword has a key (or with use_fast_todo_selection = false), <C-c><C-t> cycles within the current sequence only: after its last keyword the heading has no keyword, and the next <C-c><C-t> starts that same sequence again. Run this block to switch fast selection off for this session:

require("org.config").opts.use_fast_todo_selection = false

Try: on "Crash when saving an empty file", press <C-S-Right>. Expect: TODO Crash when saving an empty file and the message Keyword-Set 1/2: TODO NEXT WAITING DONE CANCELLED. Press it again to get REPORT back.

In Lua the same definition is a list of strings, one per sequence. File lines replace the configured keywords for that file.

require("org").setup({
  todo_keywords = {
    "TODO(t) NEXT(n) WAITING(w@/!) | DONE(d!) CANCELLED(c@)",
    "REPORT(r) BUG(b) KNOWNCAUSE(k) | FIXED(f!)",
  },
})

Without any |, the last keyword of a sequence is its done state: #+TODO: TODO DOING DONE has DONE as done state.

Try: delete the # and the space in front of #+TYP_TODO: above, press <C-c><C-c> on that line (message "Local setup has been refreshed"), run the Lua block, then on "Review the budget" press <C-c><C-t>. Expect: FRED Review the budget.

Try: press $ (the cursor moves, so the next one is a new command), then press <C-c><C-t> once. Expect: DELEGATED Review the budget with a CLOSED: line: from a type it jumps straight to the done state.

Try: press <C-c><C-t> to clear it, then <C-c><C-t> three times without moving. Expect: FRED, then SARA, then LUCY.

When you are done, put the # and a space back in front of the #+TYP_TODO: line and press <C-c><C-c> on it again (or u until it is back).

Try: on "Pack the suitcase", press <M-S-CR> and type Book a taxi, then <Esc>. Expect: a new heading TODO Book a taxi after the text of "Pack the suitcase" (a new heading always goes after the whole subtree).

Try: on "Send the invoice", press <C-c><C-t> then d. Expect: three lines:

*** DONE Send the invoice
CLOSED: [2026-09-28 Mon 15:08]
- State "DONE"       from "TODO"       [2026-09-28 Mon 15:08]

The CLOSED: line comes from logdone; the - State line comes from the ! in DONE(d!), see the next section.

Try: press <C-c><C-t> then t. Expect: TODO Send the invoice; the CLOSED: line is gone (the state line stays).

Other #+STARTUP: words for the same setting:

Like Emacs, CLOSED: is only added when logdone (or log_done) is on: a ! on the DONE keyword alone gives the - State line but no CLOSED:. closed_keep_when_no_todo = true keeps CLOSED: when the keyword is removed completely.

Try: on "Get the car repaired", press <C-c><C-t> then w. In the *Org Note* window type Garage opens on Monday and press <C-c><C-c>. Expect:

*** WAITING Get the car repaired
- State "WAITING"    from "TODO"       [2026-09-28 Mon 15:08] \\
  Garage opens on Monday

Try: now press <C-c><C-t> then n. Expect: a new line on top of the first one (newest first): - State "NEXT" from "WAITING" [2026-09-28 Mon 15:08]. There was no note: leaving WAITING only logs the time (/!).

Try: press <C-c><C-t> then c, and in the note window press <C-c><C-k> (cancel). Expect: CANCELLED Old gym membership with a CLOSED: line, but no - State line: a cancelled note logs nothing, the state change stays.

• State "WAITING" from "TODO" [2026-09-22 Tue 09:12]
  Emailed the landlord about the heating.

Try: on "Plan the team dinner", press 4<C-c><C-t> then n, type Waiting for the head count and press <C-c><C-c>. Expect: NEXT Plan the team dinner and a log item - State "NEXT" from "TODO" [...] \\ followed by the note.

Try: press <C-c><C-z>, type Booked Luigi's for Friday, <C-c><C-c>. Expect: a new item on top: - Note taken on [2026-09-28 Mon 15:08] \\ and your text below it.

Try: type :Org todo_without_note and press <CR>, then w. Expect: WAITING with a line - State "WAITING" from "NEXT" [...] and no note window.

Try: on "Pay the rent", press <C-c><C-t> then d. Expect: the heading is TODO again (not DONE), the deadline shows 2026-11-01 Sun +1m, and under it:

:PROPERTIES:
:LAST_REPEAT: [2026-09-28 Mon 15:08]
:END:
- State "DONE"       from "TODO"       [2026-09-28 Mon 15:08]

Try: mark "Weekly team meeting notes" done. Expect: SCHEDULED: shows 2026-10-05 Mon ++1w: three weeks were missed, and ++ jumped over all of them to the first Monday after today. A plain +1w would have given 2026-09-14, still in the past.

Try: mark "Water the plants" done. Expect: SCHEDULED: shows 2026-10-01 Thu .+3d: three days after today, no matter when it was last scheduled.

Try: mark it done. Expect: DEADLINE: shows 2026-10-30 Fri +1m -5d (the warning period stays).

Try: mark it done. Expect: both dates move one year: 2027-10-12 Tue +1y and 2027-11-15 Mon +1y (org.nvim writes DEADLINE: first on the line).

Try: mark it done. Expect: 2026-09-28 Mon 12:00 +2h, two hours later on the same day.

Meets on <2026-10-06 Tue 19:00 +1w>. Try: mark it done. Expect: the timestamp in the body becomes 2026-10-13 Tue 19:00 +1w: plain active timestamps with a repeater shift too.

Try: mark it done. Expect: NEXT Stand-up notes (not TODO), scheduled 2026-09-29 Tue +1d, and a LAST_REPEAT line in the drawer.

Try: type :Org todo_cancel_repeaters and press <CR>, then d. Expect: DONE Physiotherapy exercises, and the planning line reads CLOSED: [2026-09-28 Mon 15:08] SCHEDULED: followed by 2026-09-29 Tue .+0d in angle brackets: the task no longer repeats.

Try: press <prefix>a then a (week agenda), go to today. Expect: under today, a line todo: TODO Go for a run followed by a graph starting at column 40 (agenda.habits.graph_column), 21 days back and 7 ahead: * on the five days of the :LOGBOOK: and ! on today, colored as in the table above. On a later day the last days turn red: the habit is overdue.

Try: back here, mark the habit done, then refresh the agenda (r). Expect: SCHEDULED: becomes two days from today, and a new - State "DONE" line is at the top of the :LOGBOOK:. The habit is gone from today's agenda: it is not due again before that date (habits are only shown for today, agenda.habits.show_habits_only_for_today).

Try: on "Move to the new flat", press <C-c><C-t> then d. Expect: the message TODO state change from TODO to DONE blocked (by has unfinished child tasks) and the heading is unchanged.

Try: mark "Hire the movers" done, then "Move to the new flat". Expect: both are DONE now.

Try: on a blocked parent press 64<C-c><C-t> (Emacs C-u C-u C-u C-c C-t) and pick d. Expect: the change goes through even though children are open.

Try: mark "Bake for 40 minutes" done. Expect: the message TODO state change from TODO to DONE blocked (by previous sibling (ORDERED) is not done: Mix the dough): it names the first open sibling.

Try: mark "Mix the dough" done, then "Let it rise", then "Bake for 40 minutes", then "Bake bread". Expect: each one works in this order.

Try: on "Bake bread", press <C-c><C-x>o. Expect: the :ORDERED: line disappears and the message "Subtasks can be completed in arbitrary order".

Try: mark "Launch the website" done. Expect: it works although its child is open, thanks to NOBLOCKING.

Try: press <prefix>a then m, type BLOCKED"t"= and <CR>. Expect: "Paint the fence" is listed (its child is open), "Buy paint" is not.

• [X] Passport
• [ ] Charger
• [ ] Toothbrush

Try: run the block, then mark "Pack for the trip" done. Expect: ... blocked (by contained checkboxes).

Try: check the other two boxes with <C-Space> on each, then mark it done. Expect: the cookie shows [3/3] and the task becomes DONE.

Done states all count as done, CANCELLED included.

Try: on the cookie [1/4] press <C-c><C-c>. Expect: [2/4]: the cookie was out of date on purpose (CANCELLED is a done state too).

Try: mark "Invite the speakers" done. Expect: [3/4].

Try: mark the children done one by one. Expect: [33%], [66%], [100%] (percentages are rounded down).

Try: press <C-c><C-c> on either cookie. Expect: [1/2] [50%].

Try: with the cursor on this heading, press <prefix>#. Expect: [0/0]: no children, nothing to count.

Try: press <C-c><C-c> on [0/5]. Expect: [1/5] (one of the five is done).

Try: mark "Linux" done. Expect: [2/5]; "Test on all platforms" can now be marked done too.

• [X] Pick a title
• [X] Write the abstract
• [X] Book the room

Try: press <C-c><C-c> on the cookie. Expect: still [0/2]: the two child tasks are counted, not the three checked boxes. Delete the :COOKIE_DATA: line (and the now empty drawer), press <C-c><C-c> on the cookie again: [3/3].

Try: run the block, then mark "Vacuum" and "Laundry" done. Expect: after the second one, the parent turns into DONE Weekend chores [2/2] by itself. Set a child back to TODO and the parent goes back to TODO.

require("org.config").opts.after_todo_statistics_hooks = {}

Try: on "Call the insurance", press <S-Up>. Expect: TODO [#C] Call the insurance (the default).

Try: press <S-Up> twice more, then once more. Expect: [#B], [#A], then the cookie is removed (message "Priority removed").

Try: press <S-Up> again. Expect: [#E]: it wrapped around to the lowest priority.

Try: put the cursor on the B of [#B] and press <C-x>, then <C-a> twice. Expect: [#C], then [#B], then [#A].

Try: press <prefix>, then d. Expect: [#D]. With <prefix>, then <Space> the cookie disappears. <prefix>, then z says "Priority must be between A and E".

Try: press 4<prefix>,. Expect: the message "Priority is 1000" for [#D] (1000 × (E − D)).

Try: change the header line of this file to #+PRIORITIES: 1 10 5, press <C-c><C-c> on it, then on this heading press <prefix>,, type 3 and press <CR>. Expect: TODO [#3] A task for numeric priorities.

Try: press <S-Down>, then <S-Up> twice. Expect: [#4], then [#3], then [#2].

Put the header back to #+PRIORITIES: A E C (and <C-c><C-c> on it) afterwards; with the numeric range, the letter cookies of this file are out of range, and :Org lint reports them.