StandardForm

by Phil Baum
5
4
3
2
1
Score: 51/100

Description

The StandardForm plugin for Obsidian is a must-have for anyone working with logic, philosophy, or formal notation. This plugin transforms logical statements written in code blocks into neatly styled renderings, making complex logical reconstructions much easier to read and understand. Designed for enthusiasts of structured reasoning, it enhances clarity without compromising on detail.

To use the plugin, simply define your logical statements within standardform code blocks. It supports labeled premises and conclusions, as well as minimal formatting for clean visual organization. Whether you're outlining arguments or working through logical proofs, the plugin streamlines the process with elegant and accessible outputs.

Ideal for academics, students, or anyone tackling formal reasoning, StandardForm elevates your Obsidian vault's capability for presenting logical frameworks, ensuring that your work is both visually appealing and highly readable.

Reviews

No reviews yet.

Stats

9
stars
599
downloads
0
forks
534
days
305
days
305
days
1
total PRs
0
open PRs
0
closed PRs
1
merged PRs
5
total issues
1
open issues
4
closed issues
29
commits

Latest Version

10 months ago

Changelog

  • Bind conclusion line to text-color to fix darkmode (#5)

README file from

Github

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 ==)