Re: [O] babel result chain outdated/inconsistent using var

2016-04-07 Thread Daniele Pizzolli
On Thu, Apr 07 2016, Nicolas Goaziou wrote: > Daniele Pizzolli writes: > >> Do I am missing something else? Thanks again for your assistance. > > There seems to be an issue with cache. Call `M-x > org-element-reset-cache' before calling `org-babel-execute-buffer'. Hello, thanks, to be precise t

Re: [O] babel result chain outdated/inconsistent using var

2016-04-07 Thread Nicolas Goaziou
Daniele Pizzolli writes: > Do I am missing something else? Thanks again for your assistance. There seems to be an issue with cache. Call `M-x org-element-reset-cache' before calling `org-babel-execute-buffer'. Regards,

Re: [O] babel result chain outdated/inconsistent using var

2016-04-07 Thread Daniele Pizzolli
On Thu, Apr 07 2016, Nicolas Goaziou wrote: > Hello, > > Daniele Pizzolli writes: > >> #+NAME: pid-result >> #+RESULTS: pid >> #+NAME: echo-pid >> #+BEGIN_SRC shell :var DATA=pid-result :results value >> printf '%s' "${DATA}" #+END_SRC >> >> #+RESULTS: echo-pid > > You are giving two names to the

Re: [O] babel result chain outdated/inconsistent using var

2016-04-07 Thread Nicolas Goaziou
Hello, Daniele Pizzolli writes: > #+NAME: pid-result > #+RESULTS: pid > #+NAME: echo-pid > #+BEGIN_SRC shell :var DATA=pid-result :results value > printf '%s' "${DATA}" #+END_SRC > > #+RESULTS: echo-pid You are giving two names to the block, which is not possible. I don't know what you are tr

Re: [O] babel result chain outdated/inconsistent using var

2016-04-07 Thread Daniele Pizzolli
On Wed, Apr 06 2016, Nicolas Goaziou wrote: > Daniele Pizzolli writes: > >> Thanks Nicolas for the reply. Ok, but `org-babel-execute-buffer' >> produces an inconsistent document right now. > > This is because you ask it to. See below. > >> Mmm, the same reasoning can be used for arguing about the

Re: [O] babel result chain outdated/inconsistent using var

2016-04-06 Thread Nicolas Goaziou
Daniele Pizzolli writes: > Thanks Nicolas for the reply. Ok, but `org-babel-execute-buffer' > produces an inconsistent document right now. This is because you ask it to. See below. > Mmm, the same reasoning can be used for arguing about the current > behaviour: If I C-c C-c on a block, I expec

Re: [O] babel result chain outdated/inconsistent using var

2016-04-06 Thread Daniele Pizzolli
On Wed, Apr 06 2016, Nicolas Goaziou wrote: > Hello, > > Daniele Pizzolli writes: > >> is possible to update the “#+RESULTS: pid” when the block “#+NAME: >> echo-pid” is evaluated in the following snippet? > > Without `org-babel-execute-buffer', I don't think so. Hello, Thanks Nicolas for the r

Re: [O] babel result chain outdated/inconsistent using var

2016-04-06 Thread Nicolas Goaziou
Hello, Daniele Pizzolli writes: > is possible to update the “#+RESULTS: pid” when the block “#+NAME: > echo-pid” is evaluated in the following snippet? Without `org-babel-execute-buffer', I don't think so. > This will lead to a consistent document generation with “M-x > org-babel-execute-buffe

[O] babel result chain outdated/inconsistent using var

2016-04-06 Thread Daniele Pizzolli
Hello, is possible to update the “#+RESULTS: pid” when the block “#+NAME: echo-pid” is evaluated in the following snippet? This will lead to a consistent document generation with “M-x org-babel-execute-buffer” or by hitting “C-c C-c” on “#+NAME: echo-pid”. Using the cache does not make sense: th