From: "Berry, Charles" <ccberry@ucsd.edu>
To: Dmitrii Korobeinikov <dim1212k@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [Proposal] Source Blocks with Post-Extensions
Date: Mon, 22 Apr 2019 16:51:23 +0000 [thread overview]
Message-ID: <AAB30FFE-1534-40CE-8B45-FAB385C150A2@ucsd.edu> (raw)
In-Reply-To: <CA+Yh0SQKnaGJyGGqOpZm8jamguGTCvmHLRdYZbu2GUDWZwYACQ@mail.gmail.com>
It looks like you want the :epilogue header argument. See inline.
> On Apr 22, 2019, at 2:00 AM, Dmitrii Korobeinikov <dim1212k@gmail.com> wrote:
>
> When I write several source blocks, which depend on one another, I tend to debug them one by one.
>
> So, I write this function and test it:
>
> #+NAME: square
> #+BEGIN_SRC python
> square = lambda x: x * x
> return square(5)
> #+END_SRC
>
> #+RESULTS: square
> : 25
>
Equivalently, you could run this:
#+NAME: square
#+BEGIN_SRC python :epilogue return square(5)
square = lambda x: x * x
#+END_SRC
> After I see that the test is successful, I write this client function:
>
> #+BEGIN_SRC python :noweb yes
> <<square>>
> return 5 + square(5)
> #+END_SRC
>
> #+RESULTS:
> : 25
>
> And here, to get the correct result, I have to remove the ~return square(5)~ line in ~<<square>>~.
> But I don't want to lose testing!
> S
With my version of `square`, the epilogue is not included.
So it works as you want it to.
HTH,
Chuck
next prev parent reply other threads:[~2019-04-22 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 9:00 [Proposal] Source Blocks with Post-Extensions Dmitrii Korobeinikov
2019-04-22 16:51 ` Berry, Charles [this message]
2019-04-22 17:15 ` Dmitrii Korobeinikov
2019-04-22 17:31 ` Berry, Charles
2019-04-24 19:05 ` Dmitrii Korobeinikov
2019-06-26 22:09 ` Martin Alsinet
2019-07-03 16:02 ` Dmitrii Korobeinikov
2019-07-26 12:02 ` Ken Mankoff
2019-07-26 12:58 ` Martin Alsinet
2019-07-26 15:18 ` Ken Mankoff
2019-07-26 15:52 ` Martin Alsinet
2019-04-22 20:59 ` Tim Cross
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=AAB30FFE-1534-40CE-8B45-FAB385C150A2@ucsd.edu \
--to=ccberry@ucsd.edu \
--cc=dim1212k@gmail.com \
--cc=emacs-orgmode@gnu.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.
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).