public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Niklas Dewally <niklas.dewally-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Do Obsidian.md Callout filters exist?
Date: Fri, 2 Sep 2022 09:07:42 -0700 (PDT)	[thread overview]
Message-ID: <f349a7a8-a9aa-4d92-92ea-fc24ed3bb66fn@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1677 bytes --]

I use Obsidian.MD for note taking, and it supports admonitions / callouts 
as part of its markdown syntax.

There currently are a few pandoc related plugins inside obsidian, however 
these all use a custom approach of grabbing the javascript / html from the 
apps live-preview and inserting it. 

I would much prefer to use a filter so that I can stay in the command line 
and be able to treat it more like standard markdown in the pandoc ecosystem.

I see that a LaTeX plugin exists, and some stack overflow snippets [1;2], 
but nothing that supports Obsidian syntax. I also wish to use HTML as well 
as TeX.

I would imagine that would be a somewhat common use-case for Obsidian, 
given the apps focus on storing things as plain-text markdown! Does anyone 
know / have written a filter that does something like this (so that I don't 
duplicate work unnecessarily)!


For those unfamiliar with obsidian, it does callouts as ![<type>], followed 
by a quote block. E.g.

![NOTE]-
> callout
> here
> `some code`
> *italics*

I don't know if this is syntax used elsewhere or not.

Thanks,
Nik

1: https://pandoc-latex-admonition.readthedocs.io/en/latest/
2: https://stackoverflow.com/questions/73049303/convertng-markdown-admonition-syntax-to-html-using-lua-for-pandoc

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/f349a7a8-a9aa-4d92-92ea-fc24ed3bb66fn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2300 bytes --]

                 reply	other threads:[~2022-09-02 16:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f349a7a8-a9aa-4d92-92ea-fc24ed3bb66fn@googlegroups.com \
    --to=niklas.dewally-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).