eddie516 downloadsAdd timestamps to entries under dated headers for lab notebook style logging.
Timelog is an Obsidian plugin designed for lab-style note taking. I keep a single markdown document per project (for example My Project Log), add a dated heading for each work session, and capture new thoughts as bullet points under that heading. Timelog removes the busywork of stamping times and jumping between sections so you can stay focused on the work itself.
The plugin uses your Daily Note settings (if enabled) to match your preferred date format; otherwise it falls back to ISO YYYY-MM-DD.
## [[YYYY-MM-DD]]).Example snippet:
## [[2024-05-11]] – Undocumented REST API
- **08:45**: Collected notes from the old Confluence page; spotted a missing auth header.
- **09:30**: Sent a `GET /customers/123` request with `X-Legacy-Token`; saved the 401 response.
- **09:42**: Retried with `Authorization: Legacy token=...`; success, captured JSON body.
- **13:05**: Listed follow-up tests to map the remaining verbs.
HH:mm) at the cursor while you type bullet points.YYYY-MM-DD).| Command | Description |
|---|---|
| Start log entry | Inserts a new dated level-2 heading (## [[YYYY-MM-DD]]) and places the cursor beneath it. |
| Jump to latest log header | Scrolls to the newest dated heading, ensures there is writing space, and focuses the cursor just below the heading. |
Assign hotkeys to these commands in Obsidian’s settings for quick access.
Open Settings → Community Plugins → Timelog to configure:
HH:mm).Changes update the status bar immediately so you always see the current interval.
main.js and manifest.json into your vault at Vault/.obsidian/plugins/obsidian-time-log/.npm install
npm run dev
The dev script recompiles main.ts to main.js whenever you save. Symlink the project into your vault for hot reloading if you use a development plugin that supports it.
Example (adjust paths to your vault):
ln -s ~/src/obsidian-time-log ~/Documents/Obsidian/.obsidian/plugins/obsidian-time-log
This repo uses a GitHub Actions workflow that publishes artifacts whenever you push a version tag.
Bump the version in manifest.json and package.json (the npm run version helper can update manifest.json and versions.json for you).
Update versions.json with the new version → minimum Obsidian version mapping.
Run npm run build.
Commit your changes and tag the release:
git tag -a 1.0.1 -m "1.0.1"
git push origin 1.0.1
The GitHub Action uploads manifest.json and main.js as release assets automatically.
MIT