all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Brand <michael.ch.brand@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Achim Gratz <Stromeko@nexgo.de>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: evaluation context in call statements
Date: Wed, 26 Jun 2013 10:38:31 +0200	[thread overview]
Message-ID: <CALn3zoiou-sf12V7Vs235UKsTjLWwtL2AQJYnAVm-KEdtN_NMA@mail.gmail.com> (raw)
In-Reply-To: <87ip11h2zq.fsf@gmail.com>

Hi Eric

On Wed, Jun 26, 2013 at 12:41 AM, Eric Schulte <schulte.eric@gmail.com> wrote:
> I think we could be well served by discussing how people use call lines,
> how they would use call lines (if this behavior changed), and what
> behavior would best support these existing and potential use cases.

You did not yet answer to what I asked you about more than one call
with the same arguments:
http://thread.gmane.org/gmane.emacs.orgmode/72513/focus=73547

> In defense of the existing behavior, I don't see the benefit of calling
> a code block with the same arguments from multiple locations and
> subsequently littering a file with multiple identical results blocks.

Such result blocks do not have to be necessarily identical. What would
you suggest for these examples?:

1) It could be just me feeling like to be on the playground:
   -------------------------------------------------------------------
   #+NAME: i_am_curious_how_this_works
   #+BEGIN_SRC emacs-lisp
     (format "%s" org-babel-current-src-block-location)
   #+END_SRC

   #+CALL: i_am_curious_how_this_works()

   #+RESULTS: i_am_curious_how_this_works()
   : #<marker at 124 in tmp.org>

   #+CALL: i_am_curious_how_this_works()

   (Here I expect to see the result "#<marker at 235 in tmp.org>".)
   -------------------------------------------------------------------

2) My use case mentioned at the beginning of this message.

Michael

  parent reply	other threads:[~2013-06-26  8:38 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALn3zoiou-sf12V7Vs235UKsTjLWwtL2AQJYnAVm-KEdtN_NMA@mail.gmail.com \
    --to=michael.ch.brand@gmail.com \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.