From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Literate programming in org
Date: Wed, 26 Aug 2015 22:07:55 +0200 [thread overview]
Message-ID: <861tepertw.fsf@example.com> (raw)
In-Reply-To: 55DE164A.6050509@gmx.de
Max Linke <max_linke-Mmb7MZpHnFY@public.gmane.org> writes:
> On 08/26/2015 12:36 PM, Sebastien Vauban wrote:
>> See:
>>
>> - inline Babel calls: ... call_<NAME>(<ARGUMENTS>) ... and/or
>> - inline code blocks: src_<LANGUAGE>{<BODY>}.
>
> Yes I'm currently using inline babel calls.
>
>>> * 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 don't understand why re-running code blocks which are cached is
>> a problem. Could you elaborate?
>
> I wanted a shortcut to rerun every code cell independent of cached
> status. Looking again into the docs I found the short-cut
>
> 'C-u C-c C-v b'
>
> This calls 'org-babel-execute-buffer'.
... to forcibly re-evaluate the blocks (even when marked ":cache"), yes.
OK, got it now!
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2015-08-26 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 8:35 Literate programming in org Max Linke
2015-08-26 10:36 ` Sebastien Vauban
2015-08-26 19:40 ` Max Linke
2015-08-26 20:07 ` Sebastien Vauban [this message]
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=861tepertw.fsf@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@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.
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).