No description
Find a file
2026-05-14 10:27:37 +02:00
.github/workflows Update release.yml 2026-05-14 10:27:37 +02:00
src address Obsidian plugin review and clean up dev deps 2026-05-14 10:27:04 +02:00
test add vitest test suite, CLAUDE.md, and parser/renderer fixes 2026-05-14 10:12:22 +02:00
.editorconfig Initial commit 2024-11-02 21:16:29 +01:00
.gitignore Initial commit 2024-11-02 21:16:29 +01:00
.npmrc Initial commit 2024-11-02 21:16:29 +01:00
CLAUDE.md address Obsidian plugin review and clean up dev deps 2026-05-14 10:27:04 +02:00
demo.png new release 2025-04-26 14:34:20 +02:00
esbuild.config.mjs address Obsidian plugin review and clean up dev deps 2026-05-14 10:27:04 +02:00
LICENSE Create LICENSE 2024-11-06 19:52:55 +01:00
Makefile add vitest test suite, CLAUDE.md, and parser/renderer fixes 2026-05-14 10:12:22 +02:00
manifest.json address Obsidian plugin review and clean up dev deps 2026-05-14 10:27:04 +02:00
package-lock.json address Obsidian plugin review and clean up dev deps 2026-05-14 10:27:04 +02:00
package.json address Obsidian plugin review and clean up dev deps 2026-05-14 10:27:04 +02:00
README.md adjust 2025-04-26 14:36:39 +02:00
styles.css couple conclusion lines to text color to fix dark mode issue 2025-07-07 19:56:05 +02:00
tsconfig.json Initial commit 2024-11-02 21:16:29 +01:00
versions.json address Obsidian plugin review and clean up dev deps 2026-05-14 10:27:04 +02:00
vitest.config.ts add vitest test suite, CLAUDE.md, and parser/renderer fixes 2026-05-14 10:12:22 +02:00

StandardForm

A plugin for Obsidian that transforms code blocks with logical Standard Form syntax into clean, styled renderings, enhancing readability of logical reconstructions. Perfect for philosophy, logic, and formal notation.

Demo

Demo showing rendered code blocks

Usage

To enable parsing, code blocks have to be specified as "standardform" language.

```standardform
1. If someone is a programmer, then they prefer tools that support Markdown.
2. If someone prefers tools that support Markdown, then they enjoy using Obsidian.
 -- CI (1, 2) --
IC: If someone is a programmer, then they enjoy using Obsidian.
3. Phil is a programmer.
-- MP (IC, 3) --
C: Phil enjoys using Obsidian.
```
```standardform
if p, then q
not q
--
not p
```

Format

  • Identifiers must end with either a colon (:) or a period (.), such as P1:, C1., or Something:.
    • If you want to use a colon or period in your premisse or conclusion text, it needs to be escaped with a backslash: Some text\. More text.
  • Identifiers can be ommited.
  • Conclusion lines can be written either as -- any text -- or simply -- to create a line without text.
    • To indicate a inductive inference, == can be used to draw a double line (also works with == text ==)