From: Julianus Pfeuffer <jule.pf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: ipynb output: Choose languages to convert to code cells
Date: Tue, 21 Sep 2021 06:46:42 -0700 (PDT) [thread overview]
Message-ID: <e539846c-74da-4636-82ea-f63cfcf8ee0bn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 983 bytes --]
Hi all,
does anyone know of a way, how to decide which code language to convert to
an ipynb code cell?
The default is "code" but of course no one would just use "code" as a
language description in input formats that are not specifically written for
this pandoc conversion to ipynb.
I am envisioning to be able to specify e.g. python, R as languages of my
input code blocks (as long as the input format supports a language tag,
e.g. Markdown or rst) which should be converted to executable code cells in
the notebook.
Is this possible?
Thanks and cheers
Julianus
--
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/e539846c-74da-4636-82ea-f63cfcf8ee0bn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1378 bytes --]
next reply other threads:[~2021-09-21 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 13:46 Julianus Pfeuffer [this message]
[not found] ` <e539846c-74da-4636-82ea-f63cfcf8ee0bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-21 16:04 ` John MacFarlane
[not found] ` <m2wnn9hq4u.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-09-21 17:16 ` Julianus Pfeuffer
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=e539846c-74da-4636-82ea-f63cfcf8ee0bn@googlegroups.com \
--to=jule.pf-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).