Capture optimizes interruption; Refile restores structure. Their connecting practice is a regular inbox review.
Thought, then inbox, then a home
thought → capture → inbox.org → review → refile → project, note, or task
~/org/
├── inbox.org quick unprocessed capture
├── projects.org outcomes and next actions
├── notes.org durable reference
└── journal.org chronological recordA template earns its key. Twenty templates usually mean the review habit is missing.
Capture separates fast recording from later classification:
thought → capture → inbox.org → review → refile → project, note, or taskBind org-capture globally, then add a few templates. Each entry has a key, description, capture type, target, and template. %? leaves point for editing; %U inserts an inactive timestamp; %i includes the active region; %a stores an annotation link. Clipboard capture can expose sensitive data; use it deliberately.
Finish with C-c C-c or abort with C-c C-k. Avoid twenty templates. A template earns its place when it captures distinct metadata or targets a genuinely different review process.
Refile moves a heading with C-c C-w. Full outline-path completion disambiguates repeated headings. During review, clarify the captured item, make it actionable if necessary, refile it, or delete it. Capture without review merely creates a trusted pile of forgotten text.
Summary. Capture optimizes interruption; Refile restores structure. Their connecting practice is a regular inbox review.
Exercises
- Basic: Capture one task and finalize it.
- Practical: Capture a bookmark with annotation, then refile it under a project.
- Advanced: Add a meeting template with title, participants property, timestamp, and action-item subtree.