ZenNotes v2.7.0
ZenNotes 2.7.0 — link straight to your CSV databases, / slash commands in Quick Capture, and editor fixes.
Installers for macOS, Windows, and Linux are attached below once the build finishes. On macOS,
brew install --cask zennotes/tap/zennotes; on Arch,yay -S zennotes-bin.
✨ Highlights
Link to a database with [[wikilinks]] (#238)
Your CSV databases (.base folders) are now first-class wikilink targets — type [[ and they show up in the picker alongside notes and assets, tagged DATABASE. Pick one to drop a [[My Database]] link, then click it (in the editor, in source mode, or in the preview pane) to jump straight to the grid. Previously only individual record pages were linkable; now you can reference the database itself. (Requested by @AdiCahyaSaputra.)
Slash commands in Quick Capture (#182)
Quick Capture now has the same Notion-style / menu as the main editor — type / and pick a block (headings, lists, Task, quote, code, table, callout, …). Capturing a todo is now a quick /td + Enter instead of hand-typing - [ ]. Esc closes the menu without saving/hiding, and the capture window is a bit taller so the full menu shows. (Requested by @Bendzae, building on their PR #200.)
🐛 Fixes
- Undo no longer overwrites a note with a previously viewed one (#247) — after viewing one note and switching to another, pressing Cmd/Ctrl+Z reverted the editor to the first note's content and then saved it over the second note — silent data loss. Undo history is now scoped per note: switching notes resets it, so Cmd+Z can't reach across notes, while undo still works normally for edits within the current note. (Reported by @MatthewHunt84.)
- Wikilinks inside code are shown as literal code, not rendered as links (#248) — in live preview,
`[[link]]`or a[[link]]inside a fenced code block was rewritten into a clickable link instead of staying as code. The editor now leaves[[…]]alone when it sits in an inline code span or a code block (the preview pane already did), so code samples that mention wikilink syntax display verbatim. (Reported by @ryanthara.) - The document outline no longer collapses after a code block (#249) — a single-line inline code span like
```[[link]]```— or any fence-like line inside a code block — flipped the outline parser into "inside a code block" mode with nothing to flip it back, so every heading below it silently vanished and the outline showed only the headings above. The parser now tracks fenced code blocks properly (matching CommonMark — exact fence marker, length, and a real closing fence), so all your headings stay in the outline. (Reported by @ryanthara.)
Thanks to everyone filing issues — closes #182, #238, #247, #248, #249.
