ndwarshuis
/
org-mode
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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 commit is contained in:
Eric Schulte 2013-11-13 16:31:17 -07:00
parent c67e3cda15
commit d840b84bbc
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
lisp/ob-core.el
View File

@ -1929,7 +1929,10 @@ following the source block."
(cond (cond
((looking-at (concat org-babel-result-regexp "\n")) ((looking-at (concat org-babel-result-regexp "\n"))
(throw 'non-comment t)) (throw 'non-comment t))
((looking-at "^[ \t]*#") (end-of-line 1)) ((and (looking-at "^[ \t]*#")
(not (looking-at
org-babel-lob-one-liner-regexp)))
(end-of-line 1))
(t (throw 'non-comment nil)))))) (t (throw 'non-comment nil))))))
(let ((this-hash (match-string 5))) (let ((this-hash (match-string 5)))
(prog1 (point) (prog1 (point)