emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Linke <max_linke@gmx.de>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Literate programming in org
Date: Wed, 26 Aug 2015 10:35:16 +0200	[thread overview]
Message-ID: <55DD7A44.2030006@gmx.de> (raw)

Hi

I'm currently trying to use org-modes literate programming capabilities 
to write up a paper. So far it has been a joy to have the plotting code
and text in the same document. Thanks for all the work people here have
already put in to make this so easy.

I have run into a two small problems so far

* How can I use computed variables (string/int/float) in floating text?

   I have for example calculated a autocorrelation time and now want to
   use that calculated number in the text. The best solution I have
   found so far is

   #+name: print_acf_time
   #+begin_src ipython :session :exports none
     print(acf_time)
   #+end_src

   The autocorrelation time for the process is call_print_acf_time().
   That is OK-ish but I have to write a special code cell for every
   variable that I want to reference in my document. Is there another
   method to export variables to be easily accessible in org-mode?

* reruning specific cells only one time after emacs was started

   I have some cells that are long running and produce some variables
   I later use for plotting or calculating related values. To avoid
   recalculating I have added `cache: yes` to these cells. But they
   are only run once across restarts of emacs or my interpreter session
   in the background. When I start working again I would like to have a
   way to rerun all code-cells independent of the fact if they are cached
   or not. This would lead to a huge speed up in converting to latex for
   me.

I appreciate any help with this.

best Max

             reply	other threads:[~2015-08-26  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26  8:35 Max Linke [this message]
2015-08-26 10:36 ` Literate programming in org Sebastien Vauban
2015-08-26 19:40   ` Max Linke
2015-08-26 20:07     ` Sebastien Vauban
2015-08-26 12:21 ` Ken Mankoff

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=55DD7A44.2030006@gmx.de \
    --to=max_linke@gmx.de \
    --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).