emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Divan Santana <divan@santanas.co.za>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: documenting python module examples in orgmode
Date: Mon, 9 Dec 2019 09:25:21 -0500	[thread overview]
Message-ID: <CAFyQvY2cmVCqt8K32s3d3TjH7oUBMN+ihgj2=zhPv2xhTacTAA@mail.gmail.com> (raw)
In-Reply-To: <87k175dbr1.fsf@santanas.co.za>

[-- Attachment #1: Type: text/plain, Size: 643 bytes --]

On Mon, Dec 9, 2019, 5:49 AM Divan Santana <divan@santanas.co.za> wrote:

> Hi All,
> I'm trying to document python module examples in orgmode.
> I'm sure this is possible, but not quite sure how to do it.
> I'd like to define the python module in one block, and then import it in
> another.

Have you looked at the Noweb syntax?

It might so what you want (inject code from one Org src block into multiple
other src blocks).

Here's an example from my notes where I use Noweb syntax with both Python
and Nim src blocks:


[-- Attachment #2: Type: text/html, Size: 1384 bytes --]

  parent reply	other threads:[~2019-12-09 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 10:38 Divan Santana
2019-12-09 14:19 ` John Kitchin
2019-12-09 14:25 ` Kaushal Modi [this message]
2019-12-11 12:44 ` Divan Santana

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:

  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='CAFyQvY2cmVCqt8K32s3d3TjH7oUBMN+ihgj2=zhPv2xhTacTAA@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=divan@santanas.co.za \
    --cc=emacs-orgmode@gnu.org \


* 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


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).