Reference and troubleshooting
The other sections of this guide walk through Parseh one door at a time. This one is for looking things up: you arrive here with a question — a message on a page you do not understand, a word the other pages use without explaining it, a file you want to find on the disk — and leave with the answer.
1. Which page answers what#
- When something looks wrong
- — a message a page showed you, or something that did not happen: what it means and what to do. Arranged by where you met it — starting Parseh, updating it, the guide, the books, the videos, the cards, the reading help, the studio, the exercises.
- Commands: install, serve, build
- — the installers, the server, the book builds, the two guides and the tests, every flag.
- Commands: content, lookup, Anki
- — the tools behind the reading-help downloads, the book and video pipelines, the bundles, the Anki sync and the studio’s PDF.
- The file layout
- — the folders of Parseh, and what a book, a video, a studio document, a note, an exercise deck and an Anki deck look like on the disk.
- The daily loops
- — the handful of routines most days are made of, a few steps each.
- Glossary
- — chunk, gloss, seam, run, pass, shape, jolly card and the rest: the words Parseh uses, each in a sentence or two.
- What changed, version by version
- — every version, newest first, and what it brought, each thing with a line on what it does and a link to the pages that explain it.
Almost everything is done from the pages, with a button. The few things that are not — a fresh certificate, a TeX package for large print, a book or a video put back from the trash — are on the troubleshooting page, where each comes up, with what to do by hand. The two command pages are for those who like a terminal, or who are mending something by hand.
2. Two things worth knowing first#
The page says why. When Parseh cannot do something — a recording that cannot be cut, a PDF that is behind its text, a name that is already taken — it says so on the page, in a note under the greyed-out button, in a message, in a badge or in a dialog, in a full sentence. That sentence is the best first clue; the troubleshooting page quotes the common ones.
What you read is not in Parseh. The books, the videos, the studio’s documents, your exercise decks and your Anki cards are yours: a release ships the doors and none of the content. That is why a fresh install opens on empty shelves; The file layout says what a release carries, what git keeps, and what neither ever sees.