From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: R C <recifx@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: ob-python.el: questions about output
Date: Mon, 24 Feb 2020 13:42:08 +0000 [thread overview]
Message-ID: <87sgj06r0y.fsf@ucl.ac.uk> (raw)
In-Reply-To: <CAD_Xbc6xu_bFKxOQMpdqgHjKteKGOHnarUsKJWqerP+w4XneSg@mail.gmail.com> (R. C.'s message of "Mon, 24 Feb 2020 02:13:10 -0500")
On Monday, 24 Feb 2020 at 02:13, R C wrote:
> When exported I would like the line: return 'img/ex1.png' not to be
> included in the listing of the src block.
I don't think this is currently possible in the sense you want.
You could use :noweb where you have one src block referring to others
and only output the code for the main body. E.g. something along the
lines of
#+name: mainblock
#+begin_src python :results file :noweb yes
def f(x): return np.polyval(a, x)
a = [1, -4, 4.5, -1.5]
x = np.roots(a)
print(f'Roots of the polynomial are {x}')
x_ = np.linspace(np.min(x), np.max(x), 100)
#+end_src
#+name: full
#+begin_src python :results file :noweb yes
import numpy as np
import matplotlib.pyplot as plt
<<mainblock>>
plt.plot(x_, f(x_))
plt.plot(x, f(x), marker='o')
plt.savefig('img/ex1.png')
return 'img/ex1.png'
#+end_src
Longer term, better would be an implementation of :prologue and
:epilogue options for python src blocks like we have for Maxima. It
would probably make sense to provide these options for most if not all
src blocks?
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.6-354-g9d5880
next prev parent reply other threads:[~2020-02-24 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 16:43 ob-python.el: questions about output R C
2020-02-24 4:52 ` Jack Kamm
2020-02-24 4:53 ` Jack Kamm
2020-02-24 7:13 ` R C
2020-02-24 13:42 ` Fraga, Eric [this message]
2020-02-24 16:18 ` Jack Kamm
2020-02-24 16:49 ` Fraga, Eric
2020-02-24 16:17 ` Jack Kamm
2020-02-24 16:40 ` Fraga, Eric
2020-02-27 4:29 ` R C
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=87sgj06r0y.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=recifx@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).