Skip to content

Latest commit

 

History

History
304 lines (233 loc) · 10.2 KB

syntax-differences.md

File metadata and controls

304 lines (233 loc) · 10.2 KB
Raw

Obsidian-flavored markdown vs. Logseq org-mode inspired markdown

Problem

Syntax differences

Tasks

Obsidian Logseq
- [ ] - TODO or - LATER
- [/] - DOING or - NOW
- [x] - DONE
- [-] - CANCELLED

Note

Only [ ] and [x] are standard (common?) Markdown, other symbols are the default set from the Tasks plugin that map well on the built-in Logseq statuses

Global filter

  • Obsidian Tasks: this is used to filer and treat only a subset of checkboxes as tasks

Dates

Note

For now I will focus only on the emoji-style dates (Dataview-style is similar to Logseq properties, but I don't use it anyway)

Date Obsidian Logseq
Due/Deadline 📅 YYYY-MM-DD DEADLINE: <YYYY-MM-DD ddd>
Scheduled ⏳ YYYY-MM-DD SCHEDULED: <YYYY-MM-DD ddd>
Start 🛫 YYYY-MM-DD N/A
Created ➕ YYYY-MM-DD N/A (optionally: add created:: [[YYYY-MM-DD]] property)
Done ✅ YYYY-MM-DD N/A
Cancelled ❌ YYYY-MM-DD N/A
Recurring/repeating Tasks

[!missing] Out of scope

Because Tasks plugin uses natural language dates, automatic conversion would be complicated

Priorities

Priority Obsidian Tasks Logseq
highest 🔺 [#A]
high ⏫ [#A]
medium 🔼 [#B]
normal (implicit)
low 🔽 [#C]
lowest ⏬️ [#C]

[!todo]
This mapping could be made configurable

Dependencies

[!missing] Out of scope

Although doable, it's not a priority, so for now we can ignore dependencies

Wiki-links (page links) with an alias

Frontmatter

---
aliases: ["buh", "bar"]
tags:
  - foo
  - meh
___

text
aliases:: buh, bar
tags:: foo, meh

- text

Block quotes (not required)

  • Obsidian: (standard markdown)
> some
> text
  • Logseq: (org-mode based)
#+BEGIN_QUOTE
some
text
#+END_QUOTE

Note

Logseq supports standard markdown block quotes (but not callouts!), so the conversion is not strictly required

Callouts (Admonitions)

> [!tip]
> some useful
> tip note

Type < to kick off autocompletion and list of advanced commands.
When a command is selected it expands to a BEGIN…END section inside a block. There can be multiple BEGIN…END sections in a block.

#+BEGIN_TIP
some useful
tip note
#+END_TIP

Supported block types

Obsidian callout types
  • note
  • abstract (summary, tldr)
  • info
  • todo
  • tip (hint, important)
  • success (check, done)
  • question (help, faq)
  • warning (caution, attention)
  • failure (fail, missing)
  • danger (error)
  • bug
  • example
  • quote (cite)
Logseq block types

With a potential mapping to Obsidian types:

  • ℹ️ NOTE: note/info/summary/tldr/abstract, default?
  • 💡 TIP: tip/hint/help/question/faq
  • ❗ IMPORTANT: important/attention/
  • 🔥 CAUTION: caution/todo
  • ⚠ ️ WARNING: warning/error/danger/bug/fail/failure/missing
  • 📌 PINNED: pinned/done/check/success
  • EXAMPLE: example (code block?)
  • QUOTE: quote/cite (+ standard block quote)
  • special blocks:
    • VERSE: for poetry? looks like a quote
    • COMMENT: for hidden comments (see below)
    • CENTER: actually centers the text!

Comments

Visible while editing, hidden in the preview mode.

  • Obsidian: %% comment text %% (can be inline)

  • Logseq: only block-comments (but can be in the middle of a block)

    #+BEGIN_COMMENT
comment text
#+END_COMMENT

Embeds (inline references)

[!TODO]
embedding blocks: ![[page#^reference_id]] vs. {{embed ((block reference))}}

Video embeds

Asset links

  • Obsidian: same wiki-style links as for any other files in the vault (consistency!) ![[file.pdf]] (path doesn't matter)
  • Logseq: relative links to the asset file ![](../assets/file.pdf)

Highlights (not relevant)

Note

Apparently, despite the documentation, Logseq also supports markdown syntax

Numbered lists (ordered lists)

1. one
2. two
3. three
   and a half
- one
  logseq.order-list-type:: number
- two
  logseq.order-list-type:: number
- three
  logseq.order-list-type:: number
  and a half