| commit | d840b84bbcea08facb3b6731b7b56de681f15394 | |
| author | Eric Schulte <schulte.eric@gmail.com> | |
| Wed, 13 Nov 2013 23:31:17 +0000 (13 16:31 -0700) | ||
| committer | Eric Schulte <schulte.eric@gmail.com> | |
| Thu, 14 Nov 2013 04:13:11 +0000 (13 21:13 -0700) | ||
| tree | 791b4b42a79a65b895abb9fae6c5768387c96e7c | treesnapshot (tar.gz zip) |
| parent | c67e3cda155e0a15534b5e0dfa29a1d87216d132 | commitdiff |
Don't skip call lines searching for results
This fixes a bug noticed by Rick Frankel in which two subsequent
#+call: lines will both update the same results. Before this commit
both of the following call lines would update the same result.
#+name: call-me
#+BEGIN_SRC emacs-lisp :var v="nil"
v
#+END_SRC
#+call: call-me("one")
#+call: call-me(v="two")
#+RESULTS:
: one
Now both lines are given their own result.
#+name: call-me
#+BEGIN_SRC emacs-lisp :var v="nil"
v
#+END_SRC
#+call: call-me("one")
#+RESULTS:
: one
#+call: call-me(v="two")
#+RESULTS:
: two
This fixes a bug noticed by Rick Frankel in which two subsequent
#+call: lines will both update the same results. Before this commit
both of the following call lines would update the same result.
#+name: call-me
#+BEGIN_SRC emacs-lisp :var v="nil"
v
#+END_SRC
#+call: call-me("one")
#+call: call-me(v="two")
#+RESULTS:
: one
Now both lines are given their own result.
#+name: call-me
#+BEGIN_SRC emacs-lisp :var v="nil"
v
#+END_SRC
#+call: call-me("one")
#+RESULTS:
: one
#+call: call-me(v="two")
#+RESULTS:
: two
| lisp/ob-core.el | diffblobblamehistory |