Notation Reference

LogMark uses a lightweight notation system. Everything is optional - you can always just type and hit Enter.

Entry Types

Five types: four explicit, one implicit.

PrefixShortTypeUse when...
task:t:TaskActionable, trackable, completable
idea:i:IdeaWorth preserving, not actionable yet
block:b:BlockExplicitly stuck, need a breakthrough
decision:d:DecisionChoice made, stakes matter
(none)LogJust write (Log mode)

Examples:

task: review PR by friday
t: deploy hotfix tomorrow 9am
idea: cache scores with TTL
i: what if we used WebSockets instead
block: rate limiting fails silently when Redis is down
decision: using SQLite because we need offline support
Deployed v2.3 to production
Interesting conversation about PCT theory

Short aliases (t:, i:, b:, d:) work identically to full prefixes. Use whichever is faster for you.

Routing

Project Routing

+projectname routes entries to a project folder in your vault.

+backend t: fix the memory leak
+logmark i: add export command
+client-x deployed new auth flow

The entry is saved to logmark/projects/backend/_tasks/2026.md (or the appropriate type folder). Folders are created automatically on first use.

Domain Routing

Same syntax, different purpose. Domains are for knowledge areas rather than active work.

+photography tips for low-light shooting
+ml-research i: read the attention paper
+cooking d: sourdough needs 12hr proof minimum

Domains live under logmark/domains/ instead of logmark/projects/.

Two-Level Routing

Add a scope after the route for finer organization:

+logmark/architecture d: keep vault service stateless
+backend/auth t: add rate limiting to login endpoint

Routes to logmark/projects/logmark/architecture/_decisions/2026.md.

Route Auto-Discovery

Type an unknown +route and press space. LogMark offers to create it:

  1. Choose category: project or domain (number keys)
  2. Confirm or edit the name
  3. Route is created and your entry continues

No need to visit settings or restart.

Tags

#tag adds cross-cutting themes to entries:

+backend t: fix memory leak #performance #urgent
i: cache invalidation approach #architecture

Tags are preserved in the saved entry. Use them for filtering in Obsidian or with LogMark's search.

Time References

Tasks support natural language deadlines:

InputParsed as
tomorrowNext calendar day
fridayNext occurrence of Friday
next weekMonday of next week
in 3 days3 calendar days from now
3pmToday at 15:00
EOD, COBEnd of current business day
by end of day fridayFriday at end of business day
2026-01-20Exact date

Examples:

t: review PR by friday
t: deploy hotfix tomorrow 9am
t: send quarterly report by end of day

Autocomplete

LogMark suggests completions as you type:

TriggerSuggests
+Routes from your vault
#Tags from your entries
/Commands and subcommands

Arrow keys to navigate, Enter or Tab to select, Escape to dismiss.

What Notation Does NOT Do

  • Notation in pasted content is ignored. Only your typed text affects routing and parsing. This prevents accidental routing from clipboard content.
  • No prefix means log entry. LogMark never guesses your entry type.
  • Tags and routes are preserved as-is in the saved markdown. No transformation or renaming.