From: Eric Schulte <schulte.eric@gmail.com>
To: Rick Frankel <rick@rickster.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] call results not creating #results
Date: Wed, 13 Nov 2013 16:34:18 -0700 [thread overview]
Message-ID: <87k3gb8vs2.fsf@gmail.com> (raw)
In-Reply-To: b840bb64b5385d835c45e18fe789b7e3@mail.rickster.com
Fixed, thanks for reporting.
Rick Frankel <rick@rickster.com> writes:
> Eric-
>
> Since you're looking at call lines :)...
>
> there is a (fairly new i think) bug:
>
> When searching forward for results, following call lines are not
> being respected as stop points. For instance, given:
>
> #+BEGIN_SRC org
> ,* Call block test
> ,#+name: call-me
> ,#+BEGIN_SRC emacs-lisp :var v="one"
> v
> ,#+END_SRC
>
> ,#+RESULTS: call-me
> : one
>
> ,#+call: call-me(v="two")
>
> ,#+RESULTS:
> : two
> #+END_SRC
>
> If i insert a new call-block before "two" and execute it, the following
> occurs
>
> #+BEGIN_SRC org
> ,* Call block test
> ,#+name: call-me
> ,#+BEGIN_SRC emacs-lisp :var v="one"
> v
> ,#+END_SRC
>
> ,#+RESULTS: call-me
> : one
>
> ,#+call: call-me(v="three")
>
> ,#+call: call-me(v="two")
>
> ,#+RESULTS:
> : three
> #+END_SRC
>
> as you can see, it replaced the results for call-line two.
>
> Note that if i had named "two" and executed it before adding in call
> line "three", the results would be
> ok:
>
> #+BEGIN_SRC org
> ,* Call block test
> ,#+name: call-me
> ,#+BEGIN_SRC emacs-lisp :var v="one"
> v
> ,#+END_SRC
>
> ,#+RESULTS: call-me
> : one
>
> ,#+call: call-me(v="three")
>
> ,#+RESULTS:
> : three
>
> ,#+name: two
> ,#+call: call-me(v="two")
>
> ,#+RESULTS: two
> : two
> #+END_SRC
>
> rick
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
prev parent reply other threads:[~2013-11-14 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 19:06 [BUG] call results not creating #results Rick Frankel
2013-11-13 23:34 ` Eric Schulte [this message]
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=87k3gb8vs2.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rick@rickster.com \
/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).