From: "Berry, Charles" via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: Naoya Yamashita <conao3@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Add org-md-src-block for src-block formater
Date: Thu, 27 Aug 2020 16:53:29 +0000 [thread overview]
Message-ID: <A4DAB8CC-5394-4469-8504-9BE723247FD4@health.ucsd.edu> (raw)
In-Reply-To: <CAEPcJanfnU9RnJGm5KXMYbp_7_hGUxavY-wpyS0SyV0GxAywsQ@mail.gmail.com>
You might want to browse the ox-ravel repository[1].
It provides a collection of exporters that support reformatting src blocks and inline src blocks for a variety of output formats (including markdown).
Basically, it will produce a derived backend that adds source block reformatting to whatever the parent backend provides.
It is aimed at R flavored exports (knitr, Rmarkdown, Sweave), but customizable. One can, for example, allow emacs-lisp and shell src blocks to execute during export, but format python, C++ and R blocks for markdown and subsequent processing. It is easy to apply to any markdown exporter
See ox-ravel.org for details on customization.
It has plenty of stops and whistles even without customization. Check out the examples, such as demos.org and markdown.org.
HTH,
Chuck
[1] https://github.com/chasberry/orgmode-accessories/blob/org-9-plus/markdown.org
> On Aug 26, 2020, at 10:26 PM, Naoya Yamashita <conao3@gmail.com> wrote:
>
> Hi,
> I found `ox-md` exporter drop src-block language information.
> My patch fixes the behavior; to embed src-block language information
> using markdown src block grammar.
>
> 1. Open some buffer
> 2. Tnsert below code
> 3. Turn on `org-mode`
> 4. `C-c C-e m M` (export as markdown in temp buffer)
>
> ## org source
> ```org
> #+begin_src python
> print(1 + 2)
> #+end_src
>
> #+begin_src emacs-lisp
> (print "hello")
> #+end_src
>
> #+begin_src
> something source code
> #+end_src
> ```
>
> ## before
> ```markdown
>
> # Table of Contents
>
>
>
> print(1 + 2)
>
> (print "hello")
>
> something source code
>
> ```
>
> ## after
> ```markdown
>
> # Table of Contents
>
>
>
> ```python
> print(1 + 2)
> ```
>
> ```emacs-lisp
> (print "hello")
> ```
>
> ```
> something source code
> ```
>
> ```
> <0001-Add-org-md-src-block-for-src-block-formater.patch>
prev parent reply other threads:[~2020-08-27 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 5:26 [PATCH] Add org-md-src-block for src-block formater Naoya Yamashita
2020-08-27 5:34 ` Nicolas Goaziou
2020-08-27 13:21 ` Naoya Yamashita
2020-08-27 16:53 ` Berry, Charles via General discussions about Org-mode. [this message]
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A4DAB8CC-5394-4469-8504-9BE723247FD4@health.ucsd.edu \
--to=emacs-orgmode@gnu.org \
--cc=ccberry@health.ucsd.edu \
--cc=conao3@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).