Editor settings

Five switches in Settings → Notes change how the editor behaves. Each one applies straight away, in the note pane and in any Markdown file you have open.

• Highlight the current line. The band across the line you're typing on. On by default.
• Check spelling. Misspelled words get a red underline from macOS. Nothing is corrected for you, so a name or a code word is never rewritten behind your back. Off by default.
• Auto pair brackets. Typing (, [ or { adds the closing one, typing the closer steps over it, and Delete between an empty pair removes both. With text selected, , _, `, ~ or = wraps it instead of replacing it, so twice makes it bold and = twice highlights it. Quotes are left alone, since in writing they are mostly apostrophes. Off by default.
• Indentation guides. The thin lines down a nested list, one for each level. On by default.
• Fold headings. The arrow beside a heading that hides the section under it. Off hides the arrows and opens anything folded. On by default.

The font, its size and line spacing are in Settings → Appearance, with SF Mono and Menlo for anyone who writes in a monospaced font. Surface there gives dark mode a warm sepia, a cool slate or a dim graphite ground instead of near black.

A note's tags sit in the gray strip at its foot: type one and press Enter. The arrow at the strip's right end puts it away, and the tag button in the status line underneath brings it back.

Narrow the pane and the toolbar folds rather than wrapping onto a second line: headings collapse into one menu first, then lists (with the quote), then strikethrough, code block, callouts and the picture move into the ⋯ menu and the view group shrinks to its two zoom steps, and at the narrowest width only bold, italic and link stay flat beside the menus. Every action stays reachable at every width, and keyboard shortcuts are unaffected either way.

Pictures draw in place. Hover one and two buttons appear over its corner: the magnifier opens it full size (Esc, the X or the backdrop closes it), the code button shows its markdown so you can change the path or the alt text. A click on a picture selects it; a second click opens it full size. In a Markdown file opened from Finder, a picture named by ![[name.png]] is found anywhere in the note's vault, the same way the app finds it.

The Markdown window has the note editor's header: find, AI, the outline, and the two view toggles. A file inside your vault is a note there too, with its real title (edit it to rename the file) and its star; a file from anywhere else shows its name, and its full path sits in the window's title bar.

Double-click a row to open the note in its own Markdown window. TypeFire's --- header is hidden while you edit there, and written back untouched when you save, so tags survive a round trip through the external editor.

Choosing how a note reads

Settings → Appearance carries three settings for the note body: Note font, Line height (compact, normal or relaxed) and Note text size. The font list is ten faces that ship with macOS, four sans, four serif and two monospaced, and each is shown in its own face in the menu. Code blocks and inline code stay monospaced whatever you pick.

Note version history

Pro. Every time a note is saved, TypeFire keeps a copy of what it looked like before, so you can go back. Open a note, then ⋮ → Version history (the menu at the right of the note's header).

• Kept in TypeFire's own storage, not in your vault. Nothing hidden is written into the folder you chose.
• Up to 50 versions per note, for 90 days. The most recent is always kept, however old it is.
• Restoring saves the current text to history first, so restoring the wrong version is itself undoable.
• Deleting a note forgets its history. Renaming one keeps it.