Repository navigation
ZenNotes 2.87.0 makes PDFs easier to work with. A link to a PDF page now opens at that page and marks the line it lands on, and you can copy a link to the spot you are reading. PDF exports get their own font size, Excalidraw drawings now appear in Word exports, and Vim's :set wrap controls Word wrap. Repeating tasks keep their block ids tidy, and task lists stop showing the ^id marker.
Released from 98d15ec7 through #1087 on 2026-11-18.
Features
- PDF links open at their page, and you can copy a link to where you are reading (#1085, requested by @Asterythm). A link like
[Source](assets/paper.pdf#page=3&zoom=150)used to open at page 1 unless you followed it with Vimgd. Now Cmd-click in the editor, a click in Read mode and an embed's Open button all open the PDF at its page and zoom, and following the same link again returns to that spot after you have scrolled on. To make such a link, use Copy link at the top of a PDF tab (or the link icon in the reference pane), the palette's Copy Link to PDF Location, orSpace Pin Vim mode. The link is relative to the vault, so it works pasted into a note in any folder. Desktop only; in the web app, links still open at their page. - A followed PDF link marks the line it lands on. When a link lands, a soft yellow band shows the line for about two seconds and then fades, so your eye finds it. A link that names a whole page outlines the page instead. A copied link records the line a fifth of the way down the view, and a jump puts that line back there, fully visible, instead of half hidden under the viewer's toolbar. With reduced motion on, the mark shows without fading.
- PDF exports get their own font size. Settings, Appearance, PDF export has a new Separate PDF font size switch. It is off by default, so exports print as before. Turned on, a slider from 8 to 32 px sets the size of the text on paper without touching the editor. It is saved as
pdf_export_font_sizeunder[appearance]inconfig.toml, and the web app's export follows it too. :set wrap,:set nowrapand:set wrap?in Vim (#1084, requested by @vlcinsky). The ex line now drives Word wrap::set nowraplets long lines scroll sideways,:set wrapwraps them again,:set wrap!flips it, and:set wrap?says which it is. It is the same setting as Settings, the palette's Toggle Word Wrap andAlt+Z, so all of them always agree.
Fixes
- Excalidraw drawings appear in a Word export (#1078, the Word half). A note that embeds a drawing with
![[diagram.excalidraw]]exported to Word with that text where the drawing should be. The drawing is now in the document as a picture, sized like other images. A drawing that cannot be drawn, such as a missing file, exports as its name. - A PDF card goes to its own page when that PDF is already pinned. With a PDF open in the reference pane, clicking a link card for another page of it only showed the pane, still on the old page. Each card now moves the pane to its own page, every time. In Read mode, a PDF link click and an embed's Open button also open at their page now.
- A repeating task's block id stays on the open task (#1083). A task that ends in a block id such as
^plants(so[[Chores^plants]]can link to it) copied the id onto both lines when you checked it off, so every week added another line with the same id. The id now stays on the next occurrence, so links and embeds keep showing the task you do next, and the finished record drops it. A repeating task with an id and no due date also kept its id: the newdue:used to be written after the id, which then no longer ended the line. - Task titles hide the
^idmarker. Home's Today list, the Tasks views, Kanban cards, the calendar, the timeline and reminders showed a task's block id as part of its title ("Water the plants ^plants"). They now show the title alone, the way the reading view already did. The id stays in the note. - On iPhone, iPad and Android, the repeating-task and task-title fixes come with core
core-2.87.0-core.h920b59ccb65d72a4(iPhone 1.41.0, Android 1.1.60).
For contributors
- The PDF and Word exports share one hidden export window (
withExportWindow), and the Word export reads each drawing's picture from it. Neither export changes otherwise. - The PDF viewer location is read by the desktop main process (
pdf-view-location.ts), because Chromium's PDF viewer is a frame the note page cannot script. Every read of its private state is guarded, and anything unexpected copies a plain link to the file instead. - The editor-improvements smoke suite's heading-label check now waits up to 3 seconds for its labels and prints what the editor held if they never appear, so the miss seen once at the 2.86.0 gate names its cause if it happens again.
- The repeating-task case table (
task-recurrence.cases.json) has 7 new block-id cases. zn runs the same table from its own pinned copy.
Verification
How to test locally:
- Install this release and open a vault with a PDF in it.
- PDF links: in a note, write
[Source](assets/<your pdf>#page=3&zoom=150)and Cmd-click it. Before: the PDF opened at page 1. After: page 3 at 150%, with the line marked. Scroll on, press Copy link at the top of the PDF tab, paste the link into the note and click it: the PDF returns to that spot. - PDF font size: Settings (
Cmd+,), Appearance, PDF export: turn on Separate PDF font size, drag the slider to 10 and export a long note withShift+Cmd+E. Before: the PDF used the editor's font size. After: smaller text and fewer pages, with the editor unchanged. - Word export: embed a drawing with
![[<drawing>.excalidraw]]and run Export Note as Word Document. Before: the embed text in the document. After: the drawing. :set wrap: with Vim mode on, open a note with a long line, press Escape and type:set nowrap. Before: "Unknown option: wrap". After: the line scrolls sideways;:set wrap?printsnowrap.- Block ids on a repeating task: write
- [ ] Water the plants @repeat:weekly due:2026-11-15 ^plants, put the cursor on it and pressCmd+L. Before: both lines ended in^plants, and Home listed "Water the plants ^plants". After: only the new open line keeps^plants, and Home lists "Water the plants".
Distribution channels
- GitHub: this release, latest, with all five update feeds. Every file they name was checked, and the app in both macOS DMGs is Notarized Developer ID and stapled.
- AUR:
zennotes-bin 2.87.0-1, pinned to the Linux tarball's SHA-256dc34c130…f89e39. - Homebrew: the
zennotescask in ZenNotes/homebrew-tap (359cf49). - Nix:
packaging/nix/release-data.json(248ae241), built onmain(run 44380313027). - nixpkgs: NixOS/nixpkgs#585604,
zennotes-desktop: 2.83.0 -> 2.87.0, waiting for nixpkgs review. - Self-hosted server and Docker: unchanged; server 2.84.1 is current.
- zn: this app bundles 0.17.2, the latest.
- Phones: iPhone 1.41.0 (build 63) is waiting for App Review, and Android 1.1.60 is in Play review, with its signed universal APK on the Android GitHub release. Both run core
core-2.87.0-core.h920b59ccb65d72a4from this commit. - Website: the release page and the docs on zennotes.org.
Release validation
- On
98d15ec7: typecheck, every test suite uncached (shared-domain 2701, portable-vault 398, app-core 4949, quicklook 18, web 76, desktop 1952),build:prod,npm run packand the packaged launch check (page target, rendered, 2.87.0), and the three smoke suites. No hazards, no high audit findings, no long dashes. - CI on the release PR (#1087) and on
mainpassed on every platform at98d15ec7before the tag. - The candidate core, the same artifact the phones ship, was walked on iPhone and Android, and the iPhone Cloud UI tests passed (7 passed, 1 iPad-only skip). The phone release builds were walked again on a simulator and an emulator.
- Every phone Dependabot pull request was red on a high-severity picomatch advisory that GitHub withdrew on release day; their CI passed on a re-run and they were merged.
- The Android GitHub release's first upload timed out (HTTP 408) and rolled back; it was published on a second try, and the public APK is byte-identical to Play's.
- Not tested before release: packaged Windows and Linux builds beyond CI, and the phones on real devices.