otty / dotfiles

All tools/Typora

Typora

typora

A minimal Markdown editor and reader.

Detected by typora | macOS, Linux, Windows |v2.typora.io

Version

Sync it typora@2.0.toml

Sync rules

What travels, what stays, what never leaves

Typora in your home directory Every rule on this page, by file

· ~/Library/Preferences/abnerworks.Typora.plist Sync

· ~/Library/Application Support/abnerworks.Typora/themes/ Sync

· conf/ Sync

· themes/ Sync

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/typora/1.0.tomlThe file this page is generated from

# Typora 1.x, the Electron app from typora.io (bundle id abnerworks.Typora).

# Typora 2 keeps everything in one ~/.config/Typora folder instead: see 2.0.toml.

id = "typora"

since = "1.0"

name = "Typora"

homepage = "https://typora.io"

description = "A simple yet powerful Markdown reader and editor with a seamless live preview, no split panes."

icon = "https://typora.io/img/icon_256x256.png"

# `typora` is the command the app documents for the shell. Its own

# "Use Typora From Shell or Cmd" page: on Linux "user could run `typora`

# directly in terminal"; on Windows, after adding

# {typora-installed-folder}/bin/typora.exe to PATH, "you would be able to use

# `typora xxx.md`"; on macOS the same page suggests

# `alias typora="open -a typora"`.

detect = ["typora"]

# Typora's user data directory is the platform's application-data directory

# plus "Typora": the app's own Preferences code opens the advanced settings

# with `window.Setting.userDataPath() + "/conf"` and downloads its PicGo helper

# to `userDataPath() + "/picgo/…"`

# (Contents/Resources/TypeMark/page-dist/static/js/Preferences*.js in the

# installed app). Verified on this Mac: that resolves to

# ~/Library/Application Support/Typora, which holds conf/conf.user.json and

# picgo/, and which the app's own defaults domain names back in

# WebKitLocalStorageDatabasePathPreferenceKey. On Windows the same directory is

# %APPDATA%\Typora: the support site's "Get Logs" page says "There is a

# `typora.log` under C:\Users\{username}\AppData\Roaming\Typora" and that it

# sits in the theme folder's parent. So [appData], which is exactly those three

# spellings, covers conf/ on every platform.

# Themes are the one place where macOS differs. The support site's About Themes

# page gives the macOS folder as "/Users/{username}/Library/Application

# Support/abnerworks.Typora/themes/" — named after the bundle id rather than

# the app — and this Mac's `defaults read abnerworks.Typora` confirms it, with

# currentThemeFolder pointing there. Windows and Linux keep themes under the

# user data directory instead, which is why both spellings are listed; each

# holds the same thing, the theme .css files and the *.user.css overrides the

# Custom Themes page tells users to write.

# The preferences domain is ~/Library/Preferences/abnerworks.Typora.plist —

# `defaults domains` lists abnerworks.Typora, the app binary contains the

# literal "abnerworks.Typora.plist", and the Homebrew cask's `zap trash:` names

# it beside both Application Support directories. It is where the settings

# panel writes: theme choice, fonts and colours, the image-upload and export

# settings, spell checking, the Markdown extension switches.

paths = [

"[preferences]/abnerworks.Typora.plist",

"~/Library/Application Support/abnerworks.Typora/themes/",

"[appData]/Typora/conf/",

"[appData]/Typora/themes/",

]

# The rest of the user data directory is deliberately not listed, so there is

# nothing to carve out of what is: typora.log, the Chromium profile (Cache,

# GPUCache, Local Storage, Cookies), history.data and profile.data, the

# draftsRecover and backups directories the "Auto Save, Version Control and

# Recovery" page describes, and the downloaded picgo binary.

# No whole-file credential among the paths above. Typora's licence is kept in

# the app's own local storage under the user data directory

# (~/Library/Application Support/Typora/LocalStorage on macOS), which is not

# listed here.

secret = []

# No machine_lines. The preferences file is a property list, which neither

# prefix nor key_path matching can read; conf.user.json is JSON with comments,

# which is not what a JSON parser reads either; and the theme folders are CSS.

# The machine-local parts — the recent file list, window frames, the absolute

# currentThemeFolder — all live in the plist.

# Which installed build this file describes. Typora 1.x is the

# abnerworks.Typora bundle on macOS (its Info.plist CFBundleIdentifier, the

# same id that names the preferences domain above), Typora.exe on Windows, and

# the `typora` package of the typora.io apt repository on Linux. Typora 2 kept

# the Windows and Linux names, so the version number is what tells them apart.

[version_from]

macos = ["abnerworks.Typora"]

windows = ["Typora.exe"]

linux = ["typora"]

Typora in your home directory Every rule on this page, by file

files.folderSyncexport.general.customFolder

Each machine keeps its own copy of these.

…

preferRelativePath = true

uploader = "picgo-app"

uploaderCommand = ""

picgoAppPath = "/Applications/PicGo.app"machine-local

piclistAppPath = ""machine-local

[appearance]

theme = "paper"

…

[export.general]

folderMode = "custom"

customFolder = "/Users/octocat/Documents/Exports"

pandocPath = "/opt/homebrew/bin/pandoc"machine-local

openExportLocation = false

Each machine keeps its own copy of these.

· Themes/ Sync

· Templates/ Sync

· Snippets/ Sync

· Skills/ Sync

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/typora/2.0.tomlThe file this page is generated from

# Typora 2 (Typora V2): a native host per platform — Swift on macOS, C# on

# Windows, Electron on Linux — sharing one editor. It also ships this same rule

# inside each package as its own dotfiles-rule (packaging/dotfiles-rule.toml in

# its source: Typora.app/Contents/Resources/dotfiles-rule, dotfiles-rule next

# to Typora.exe, /usr/share/dotfiles-rules/typora.toml from the .deb).

id = "typora"

since = "2.0"

name = "Typora"

homepage = "https://v2.typora.io"

description = "A minimal Markdown editor and reader."

icon = "https://typora.io/img/icon_256x256.png"

# The `typora` command: apps/macos/Typora/CLI/typora (installed from

# Settings ▸ General), apps/windows/Typora/Cli/typora.cmd, and the Linux

# package's executableName (apps/electron/electron-builder.yml).

detect = ["typora"]

# All of Typora V2's user config sits in one folder, $HOME/.config/Typora, on

# every platform — not V1's ~/Library/Application Support/abnerworks.Typora,

# ~/Library/Preferences/abnerworks.Typora.plist or [appData]/Typora/conf; V2

# reads none of those. The three hosts each hard-code the home directory plus

# ".config/Typora" and never consult $XDG_CONFIG_HOME, which is why these are

# literal `~/.config` paths and not `[configHome]`:

# Linux (Electron) apps/electron/src/main/handlers/config.ts:14

# join(homedir(), ".config", "Typora", "settings.toml");

# handlers/library.ts:23 and handlers/extensions.ts:17 use

# the same CONFIG_DIR.

# macOS (Swift) apps/macos/Typora/Handlers/ConfigCommands.swift:39-44

# homeDirectoryForCurrentUser + .config/Typora/settings.toml;

# ExtensionStore.swift:55-57 (configRoot). The app is not

# sandboxed (Typora/Typora.entitlements:

# com.apple.security.app-sandbox = false), so this is the

# real ~/.config, not a container.

# Windows (C#) apps/windows/Typora/Handlers/ConfigCommands.cs:16-18

# SpecialFolder.UserProfile + .config\Typora\settings.toml;

# LibraryCommands.cs:29-31, ExtensionCommands.cs:20-22.

# What is in that folder:

# settings.toml every setting, including key bindings (`keyBindings.config`)

# and the snippet trigger — packages/common/src/data/

# SettingsSchema.ts, written by SettingsToml.ts

# Themes/ user themes (one folder each, theme.toml …) and user.css —

# extensions.ts:21, ThemeCommands.swift:34-36,

# ExtensionStore.cs:65

# Templates/ document templates — library.ts:24-29,

# Snippets/ snippets ConfigCommands.swift:404-414,

# Skills/ the AI's skills LibraryCommands.cs:17-20

paths = [

"~/.config/Typora/settings.toml",

"~/.config/Typora/Themes/",

"~/.config/Typora/Templates/",

"~/.config/Typora/Snippets/",

"~/.config/Typora/Skills/",

]

# Deliberately not listed:

# ~/.config/Typora/Extensions/ installed extension packages (store

# downloads, language packs with ~20 MB

# dictionaries); their enabled state,

# consent and settings already travel in

# settings.toml (`extensions.*`)

# ~/.config/Typora/ExtensionData/ each extension's private storage and files

# recent.json, drafts, the document journal, AI chats and API keys, file-sync

# state — application state under [appData]/io.appmakes.Typora

# (handlers/config.ts:17, ConfigCommands.swift:53-61, ConfigCommands.cs:20-22,

# handlers/ai.ts:44, SyncCommands.swift:25-28)

# license-v2.json — Electron's userData (license/service.ts:50),

# ~/Library/Application Support/Typora (LicenseService.swift:15-17),

# %APPDATA%\Typora (LicenseService.cs:13)

# the WebView2 / Chromium profiles and logs — %LOCALAPPDATA%\Typora

# (MainWindow.cs:685-687), Electron's userData on Linux

# No `exclude`: nothing above holds state, and Otty already skips .git/,

# node_modules/, __pycache__/ and virtualenvs inside a synced directory.

# No credential among the paths above. Folder-sync passwords and tokens and

# AI keys go to the OS credential store or [appData]/io.appmakes.Typora

# (packages/workbench/src/sync/runtime.ts `secret.*`, handlers/ai.ts:74-76),

# and the licence lives outside ~/.config/Typora (see above).

secret = []

# settings.toml is read once at launch and rewritten whole from memory on the

# next change, so a rewrite under a running app is lost: side_effect stays at

# its default, true.

# settings.toml keys that name things on this machine only. Every key is

# always written (SettingsToml.ts serializeSettingsToml) and dotted keys become

# nested tables (writeNested), so these key paths always exist in the file.

[[machine_lines]]

file = "~/.config/Typora/settings.toml"

# Local folder path -> its sync binding; the binding's credentials are in this

# machine's credential store and its sync state under [appData]

# (SettingsSchema.ts `files.folderSync`, sync/folderBindings.ts). The export

# folder is a folder on this disk. Worth restoring on this device, wrong on

# any other.

match = { key_path = ["files.folderSync", "export.general.customFolder"] }

scope = "backup"

[[machine_lines]]

file = "~/.config/Typora/settings.toml"

# Where PicGo, PicList and pandoc are installed: the same on machines of one

# kind (/Applications/PicGo.app, /opt/homebrew/bin/pandoc), not across them.

match = { key_path = ["image.picgoAppPath", "image.piclistAppPath", "export.general.pandocPath"] }

scope = "platform"

# Which installed build this file describes. The macOS app's bundle id is

# io.appmakes.typora (PRODUCT_BUNDLE_IDENTIFIER in apps/macos; the .dev

# suffix is development builds only), the Windows host's executable is

# Typora.exe (AssemblyName in apps/windows/Typora/Typora.csproj), and the

# Linux .deb is the package `typora` — electron-builder names it after the

# product, Typora, since the workspace package name is scoped

# (@typemark/electron), and fpm lowercases it for dpkg. Windows and Linux keep

# Typora 1.x's names, so there the version number decides.

[version_from]

macos = ["io.appmakes.typora"]

windows = ["Typora.exe"]

linux = ["typora"]

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/typora. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these is generated from the same rules as this page. None of them splits files.folderSync and export.general.customFolder for you — that part is Otty’s own sync, or a template you write by hand.