From: Ihor Radchenko <yantar92@posteo.net>
To: JD Smith <jdtsmith@gmail.com>, Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Better support admonitions blocks
Date: Thu, 04 Apr 2024 17:04:47 +0000 [thread overview]
Message-ID: <87r0flt5xs.fsf@localhost> (raw)
In-Reply-To: <8B86B788-3B46-4879-ABDB-3AD04A7EC0CE@gmail.com>
JD Smith <jdtsmith@gmail.com> writes:
> Pandoc recently added read/write support <https://github.com/jgm/pandoc/issues/9475> for "admonitions", which are a GFM construct <https://github.com/orgs/community/discussions/16925> already supported by other org-exporters, and on GH in markdown. This refcard <https://github.com/fniessen/refcard-org-mode?tab=readme-ov-file#base-admonitions> references an org #{begin,end}_{note,warning,tip,caution,important} syntax which pandoc now follows (though it does not support the extra admonitions like danger/error/etc.).
>
> It would be nice to add org support for these 5 admonition blocks to the C-c C-, org block structure templates, and perhaps allow block face styling for these as well (ala org-src-block-faces).
CCing Adam. We recently discussed "highlight" blocks in the context of
WORG publishing.
I do not see much problem adding such blocks, although I am not sure if
we want them by default.
What we may do is to implement something akin link's :export and
:active-func parameters to allow custom fontification and export.
(... and add a new :structure-template parameter to auto-add them to
structure templates)
Then, we can add optional support for all the proposed blocks that will
define how to insert, export, and fontify them.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-04-04 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 14:04 Better support admonitions blocks JD Smith
2024-04-04 17:04 ` Ihor Radchenko [this message]
2024-04-04 21:35 ` Adam Porter
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=87r0flt5xs.fsf@localhost \
--to=yantar92@posteo.net \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
--cc=jdtsmith@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.