Pixel38 downloadsReplace typed character sequences with Unicode symbols while preserving protected Markdown contexts.
Ligature is an Obsidian plugin that immediately replaces typed character sequences with real Unicode symbols. For example, typing -> changes the Markdown source itself to →, so the result remains visible outside Obsidian.
Ligature 0.1.0 requires Obsidian 1.8.7 or later. Desktop, iOS, and Android are supported.
Enable Ligature under Settings → Community plugins.
Open Settings → Ligature to review or edit the replacement rules.
Type a configured sequence in a Markdown editor:
A -> B
The Markdown source becomes:
A → B
Use Cmd+Z on macOS or Ctrl+Z on Windows and Linux immediately after a replacement to restore ->.
| Type | Result |
|---|---|
-> |
→ |
<- |
← |
=> |
⇒ |
!= |
≠ |
<= |
≤ |
>= |
≥ |
~= |
≈ |
Each rule has a source sequence, a replacement, and an enabled state. Select Apply changes after editing.
Sources for enabled rules must be unique. One enabled source also cannot be a prefix of another, because the shorter rule would otherwise be replaced before the longer sequence could be completed. Empty values, line breaks, and rules whose source and replacement are identical are rejected.
Ligature replaces text in paragraphs, headings, lists, blockquotes, and Markdown link labels. It does not replace text in:
Only direct single-character typing triggers replacement. Paste, drag and drop, autocomplete, IME composition, programmatic edits, multiple cursors, and batch conversion of existing notes are not supported.
After Ligature is accepted into the Obsidian Community directory, search for Ligature under Settings → Community plugins.
For beta testing, add PMGWork/obsidian-ligature in BRAT. For a manual installation, download main.js, manifest.json, and styles.css from the matching GitHub release and place them in .obsidian/plugins/ligature/.
Ligature works entirely inside the active Markdown editor. It does not make network requests, collect telemetry, show ads, require an account, or read note files in the background. Settings are stored locally in the vault's plugin configuration.
npm ci
npm run dev
Run the complete release check with npm run check. Production main.js is generated locally and can be copied with manifest.json and styles.css into a test vault.