File formats, highlighting, themes and tools attach on top of the core through an API in plain C ABI. Build 1.0.0 ships fifteen plugins — they double as the reference for your own.
The base text format: gigabyte files, modes, encodings.
Markdown files: opening and saving .md and .markdown.
CSV and TSV table mode: rainbow columns, pinned header, large line numbers.
RTF documents in WYSIWYG mode: reading, editing and saving.
EPUB books laid out as a document, with a table of contents.
FictionBook 2 books laid out as a document, with a table of contents.
PDF viewing with a text layer: search, text extraction, export to PDF.
Image viewer tab: fit to window, 1:1, wheel zoom, pan, checkerboard under transparency.
Incremental highlighting for C, C++, Go, JavaScript, Python, Markdown and HTML; folding by the syntax tree.
C/C++ diagnostics over LSP, switched on in the settings.
Generates .clangd for Unreal Engine projects from UnrealBuildTool data.
Change markers, Source Control, per-hunk staging, diff and inline peek (libgit2).
Markdown preview with Mermaid diagrams, working offline.
Renders the preview in the system web engine: WebView2 on Windows, WKWebView on macOS.
HTML preview: read-only, ignores the page’s scripts and styles, loads nothing from the network.
clickable plugin pages will arrive with the catalogue — this is the list from build 1.0.0
management
your own plugin
The boundary between core and plugin is described in terms of C ABI. A boring decision with large consequences: an extension built by a different compiler, or written in a different language, keeps working.
planned, not now
A plugin store, licensing for third-party extensions and a WASM sandbox for foreign code are plans for after the public release. There are no dates and no prices. For now plugins are installed by hand, and you should only trust the ones whose source you have read.