From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastien Vauban Subject: Re: Literate programming in org Date: Wed, 26 Aug 2015 22:07:55 +0200 Message-ID: <861tepertw.fsf@example.com> References: <55DD7A44.2030006@gmx.de> <866142s5ez.fsf@example.com> <55DE164A.6050509@gmx.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Max Linke writes: > On 08/26/2015 12:36 PM, Sebastien Vauban wrote: >> See: >> >> - inline Babel calls: ... call_() ... and/or >> - inline code blocks: src_{}. > > 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