How to Use

How to use Textmind

Chronological daily log

A sprint is a level-one heading in ' It is a strict chronological log of all the day's thoughts and occurrences, divided by timestamps: [2020-01-22 Wed 00:20].

The log is lightly outlined, but the outline hierarchy is not strict. Chronology takes precedence, and pivots or digressions are encouraged, regardless of damage to the outline. A strict outline is maintained in ' to support work in ', so it isn't necessary to maintain a strict outline in '

Processing round

When to

While the log is short, it's easy to remember and use its contents. But then it gets too long, or too much time passes, or there's a big pivot. As a result, using the log causes mental friction. So it's time to do a processing round.

When is the best time for a processing round? Well, memory decays exponentially, and memory consolidation (including forgetting) occurs during nightly sleep. Spaced repetition is based on the principle that reviewing at spaced intervals stores info in long-term memory. Therefore the natural Textmind rhythm is to do one sprint per day, and process yesterday's sprint in the morning.

Sprint processing decomposes yesterday's sprint into topical headings suitable for filing in Textmind. This is a good way to review material and make decisions for today.

How to

Follow the sprint processing steps on the ' checklist. To summarize:

Duplicate yesterday's sprint. File one copy in the journal directory. Destructively analyze the other into tasks and background information. Then file the atomized headings appropriately, to depth=1. Prioritize any new tasks.

Video demo below:


Short version: Pick a task from the Org agenda and execute it as usual, using ' and '

If necessary, use a checklist to help decide the next action. This can ensure one remembers to e.g. check the day's appointments before perusing the Org agenda task list.

JIT sorting

One may need to sort the Textmind tree to complete a task. Never sort just for the sake of sorting. Always have a task that narrows focus and resolves ambiguity. In other words, use "Just-in-time" sorting.

If one can't choose a next task, then create a task, "Figure out what to do next," and sort until an answer appears. Even an open-ended question is better than purposeless sorting, and provides a surprising amount of clarification for ambiguous sorting decisions.