From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: evaluation context in call statements
Date: Tue, 25 Jun 2013 22:20:28 +0200 [thread overview]
Message-ID: <87r4fq3ptf.fsf@Rainer.invalid> (raw)
In-Reply-To: CALn3zohXL0x21gYhKj7QS0prJXDC_OcC4qgcejAqtk7b8-KytQ@mail.gmail.com
Michael Brand writes:
> Is it a bug?
I think so, but Eric has the last word on this. The results should come
after the call, but the current implementation would look for the
results line from the beginning of the buffer.
> I also noticed this when I was writing an ERT. First it confused me
> but then I thought that this is intended to make it possible to
> have #+BEGIN_SRC and #+RESULT at independent locations, possibly in
> reverse order.
I can't see how it would be much more difficult to have a #+CALL where
you want the result (independently of where the source block is), but it
seems pretty limiting to allow only a single result.
> For how to address several similar calls to different results see my
> ERT patch here
> http://thread.gmane.org/gmane.emacs.orgmode/72513/focus=73655 and the
> messages before. I used :session for emacs-lisp and a workaround with
> :var dummy_name for Babel languages that do not support :session like
> shell.
I didn't get what you were trying to do there, but it's pretty obvious
now.
Anyway, more testing shows my patch will prefer the results line after
the call, but if you then insert another call before that (without an
existing result) the result from the now second call will still be
clobbered, so there needs to be some more fixing by limiting the search
to not extend across other calls or source blocks. Or this really is a
feature, although I don't really see much use for it.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
next prev parent reply other threads:[~2013-06-25 20:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 17:34 evaluation context in call statements Rick Frankel
2013-06-25 19:21 ` Achim Gratz
2013-06-25 19:53 ` Achim Gratz
2013-06-25 20:06 ` Achim Gratz
2013-06-25 20:07 ` Michael Brand
2013-06-25 20:20 ` Achim Gratz [this message]
2013-06-25 20:55 ` Achim Gratz
2013-06-25 22:41 ` Eric Schulte
2013-06-26 6:29 ` Achim Gratz
2013-06-26 14:38 ` Rick Frankel
2013-06-26 15:13 ` Nicolas Goaziou
2013-06-26 15:29 ` Rick Frankel
2013-06-26 15:49 ` Eric Schulte
2013-06-26 15:06 ` Eric Schulte
2013-06-27 4:55 ` Achim Gratz
2013-06-27 6:22 ` Andreas Leha
2013-06-27 14:27 ` Achim Gratz
2013-06-27 23:12 ` Andreas Leha
2013-06-30 22:24 ` Eric Schulte
2013-07-01 10:23 ` Michael Brand
2013-07-01 13:11 ` Eric Schulte
2013-07-01 13:52 ` Michael Brand
2013-07-01 14:10 ` Eric Schulte
2013-06-26 8:38 ` Michael Brand
2013-06-26 14:54 ` Eric Schulte
2013-06-26 16:53 ` Michael Brand
2013-06-26 17:11 ` Eric Schulte
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=87r4fq3ptf.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/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).