TheThe0.5.0
The/Docs

Reference for version 0.4.3.

Everything below describes behaviour that exists in the build. Sections whose content must be exported from the source are marked as placeholders rather than filled with plausible text.

01 · what it is

A text editor for code, data and documents.

Publisher: Talyh. Platforms: Windows and macOS. No account, no cloud, no sync — the editor works with files on disk.

LayerWhat it is built from
CoreC++23, independent of the GUI: persistent Piece Table, memory-mapped opening, snapshot model, atomic saving
InterfaceQt 6: two design directions (Slate, Graphite), dark and light themes, window transparency
Formatstxt · csv · tsv · md · json · c · cpp · go · js · py · epub · fb2 · rtf · pdf · svg and raster images
ExtensionsPlugins over a plain C ABI; eight bundled in 0.4.3
External enginestree-sitter (highlighting), LSP/clangd (diagnostics), RE2 (regular expressions), libgit2 (git)

02 · how it works

Four decisions that define the behaviour.

2.1

The opens a file rather than loading it. From 100 MB the original is memory-mapped: pages are faulted in on access, so opening is near-instant and costs almost no RAM. The line index is built in a background thread, which keeps “go to line” and the cursor position immediate.

2.2

The buffer is a persistent Piece Table. Text is never rewritten wholesale — it is assembled from pieces — so an edit at the start of a large file costs the same as one at the end. Undo history is stored as snapshots and is effectively free.

2.3

Saving is atomic. The file on disk is replaced as a whole, so a crash or power loss during a write leaves either the entire old version or the entire new one, never a torn file.

2.4

Everything above the core is a plugin: file formats, highlighting, themes, tools. The plugin boundary is a plain C ABI, so an extension survives a compiler change and may be written in a language other than C++.

03 · modes

The mode is chosen by size and shown in the status bar.

Instead of degrading silently, the editor states which capabilities it has disabled.

ModeThresholdBehaviour
Normal< 16 MiBEverything enabled: highlighting, folding, project-wide search, git markers, language intelligence.
LargeText16 MiB — 1 GiBMemory-mapped opening, background indexing; heavy whole-file passes are constrained.
HugeSlice≥ 1 GiBWork proceeds in slices; anything that must walk the whole content is disabled deliberately.

placeholder

Exact switching thresholds and the per-mode list of disabled capabilities must be exported from the 0.4.3 source before this page is published.

How large files work in detail

04 · formats

What is read and what is written.

FormatReadWrite
txt, logsYes, gigabyte files includedYes
csv, tsvTable mode: rainbow columns, pinned headerYes, as text
mdPreview with Mermaid diagramsYes
c, cpp, go, js, pytree-sitter highlighting; clangd diagnostics for C/C++Yes
epub, fb2, rtfWYSIWYG: sheet, contents, serif typography, zoomSaved from rich text
pdfThumbnails, text-layer extractionExport only
svg, rasterBuilt-in viewerNo

The full format matrix

05 · plugins

Bundled in 0.4.3.

All are enabled with a toggle and require no rebuild of the core.

# enabled by default
plaintext   text files, encodings, large-file modes
markdown    preview, mermaid diagrams
csv         table mode for csv and tsv
json        highlighting and structure
cpp         tree-sitter grammar, smart indentation
ripgrep     project-wide search
git         markers, source control, per-hunk staging, diff

# off by default
clangd      C/C++ diagnostics over LSP, Unreal Engine projects

06 · files

A file should not suffer because you opened it.

  • Saving is atomic; the file is replaced whole rather than overwritten in place.
  • An open file is locked between processes: a second window cannot damage it silently.
  • External modification on disk raises a notification; nothing is applied without your decision.
  • Recent files and multi-root workspaces are kept per profile.

placeholder

On-disk locations — configuration directory, session state, log path per platform — are not fixed in the project materials and must be taken from the build.

07 · settings and keys

What can be configured today.

Theme (dark, light), design direction (Slate, Graphite), accent colour, separate fonts for code, interface and panels, window transparency, zoom from 50% to 400% with fit-width and whole-page modes, indentation style with auto-detection.

placeholder · keymap

The keymap is not documented in the project materials. It must be exported from the build (default keymap per platform) rather than reconstructed by analogy with other editors — a wrong shortcut in the docs is worse than a missing one.

placeholder · config file

Setting names, the configuration file format and its location must be exported from the build.

08 · limits

Known limits of 0.4.3.

Everything listed here is deliberate and documented, not a defect.

LSP: diagnostics only

Go-to-definition, hover, completion and rename are not implemented.

Five grammars

Highlighting covers C, C++, Go, JavaScript and Python.

PDF is read-only

PDF is read and exported to; editing a PDF is not supported.

Git without merge

There is diff and per-hunk staging; merge and conflict resolution are absent.

No plugin sandbox

Third-party plugins run in the editor's process. A WASM sandbox is planned.

Two platforms

Builds exist for Windows and macOS only.

What is planned, without dates

see also

Where to go next.

SDKPlugin API over C ABI, template and buildfor developers
Large filesmmap, background indexing, modes in detaildeep dive
ChangelogWhat changed in each version of the 0.4.x linedated
NoticesThird-party components and their licencesno JS
SecurityReporting a vulnerabilitycontact