Code Fence Completer

Add to Obsidian

Code Fence Completer provides reliable language suggestions when writing Markdown code fences in Obsidian.

Features

• Suggests common language identifiers after opening backtick or tilde fences.
• Supports aliases such as py, js, and ts, while inserting canonical identifiers.
• Ranks exact, prefix, substring, and fuzzy matches, then prioritizes recent languages.
• Supports custom identifiers separated by commas or new lines.
• Supports identifiers such as c++, c#, foo-bar, and foo.bar.
• Changes or clears the language of the code block containing the cursor.
• Preserves attributes after the language in a fence info string.
• Warns when another enabled plugin provides conflicting code-block suggestions.
• Avoids opening suggestions on closing fences.
• Inserts an empty code block, or wraps the current selection, with the Insert code block command.
• Works on desktop and mobile.

Usage

Type an opening fence and start entering a language:

```type

Choose a suggestion with the keyboard or pointer. The cursor moves into the code block. If there is no matching closing fence, the plugin adds one before the following document content.

You can also assign a hotkey to Code Fence Completer: Insert code block in Obsidian's Hotkeys settings.

Aliases and fuzzy search

Built-in aliases include py=python, js=javascript, ts=typescript, sh=bash, md=markdown, yml=yaml, and cs=csharp. Add custom mappings in the plugin settings using one mapping per line or comma-separated entries:

rb=ruby
kt=kotlin

Alias matches insert the canonical language. Fuzzy matching also finds identifiers when the query is a non-contiguous subsequence, such as jvs for javascript.

Change an existing code block

Place the cursor anywhere from a code block's opening fence through its closing fence, then run Code Fence Completer: Change code block language. Choose a language to replace only the first info-string token, preserving attributes such as title=demo. Choose No language to clear the entire info string.

Conflicting plugins

Only one code-block language suggester should be enabled. The plugin warns when it detects Codeblock Completer or the previous Code Language Completer plugin enabled at the same time.

Manual installation

1. Download main.js and manifest.json from the latest release.
2. Put them in <vault>/.obsidian/plugins/code-fence-completer/.
3. Reload Obsidian and enable Code Fence Completer in Community plugins.

Development

npm install
npm run check

Run npm run dev to rebuild while editing.

Release

1. Run npm version patch, npm version minor, or npm version major. This synchronizes package.json, package-lock.json, manifest.json, and versions.json, then creates the commit and tag.
2. Push the commit and version tag with git push --follow-tags.
3. The release workflow also derives the version from the tag, builds the plugin, and attaches main.js and the synchronized manifest.json to a GitHub release.

Directly pushed semantic-version tags such as v1.2.3 are supported too: the release workflow synchronizes all version files in its build checkout. Use npm version when the synchronized files should also be committed to the repository.

Manually set an exact version

Use the synchronization script to set an exact version without creating a commit or tag:

npm run sync-version -- 1.2.0

The command updates every project version location:

• package.json: the top-level version field.
• package-lock.json: both the top-level version field and packages[""].version.
• manifest.json: the version field.
• versions.json: a mapping from the new version to the current minAppVersion, for example "1.2.0": "1.13.0".

When editing the version by hand instead, update all of the same locations before committing or creating the tag.

Acknowledgements

This plugin is based on stanley-910/obsidian-code-language-completer, originally released under the MIT License. This fork includes substantial reliability, usability, testing, and release-tooling updates.