emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: :session question -- and changes to #+Property: syntax
Date: Thu, 20 Jun 2013 10:27:56 -0600	[thread overview]
Message-ID: <87ehbwsq5v.fsf@gmail.com> (raw)
In-Reply-To: <87d2rjcfsv.fsf@Rainer.invalid> (Achim Gratz's message of "Tue, 18 Jun 2013 22:41:36 +0200")

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

Achim Gratz <Stromeko@nexgo.de> writes:

> Hi Eric,
>
> while starting to write up a test document I've found some behaviour
> when executing LOB calls that warrant discussion, I think:
>
> 1. The properties are evaluated at the site of the definition rather
>    than the site of the call.

I see what you're saying.  The attached org-mode file demonstrates.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: header-eval-location.org --]
[-- Type: text/x-org, Size: 363 bytes --]

* first
  :PROPERTIES:
  :CUSTOM_ID: first
  :END:

#+name: heading-id
#+begin_src emacs-lisp :var point=(point)
  (format "%s at %d" (org-entry-get point "CUSTOM_ID") point)
#+end_src

#+RESULTS: heading-id
: first at 53

* second
  :PROPERTIES:
  :CUSTOM_ID: second
  :END:

#+call: heading-id(point=(point))

#+RESULTS: heading-id(point=(point))
: first at 53

[-- Attachment #3: Type: text/plain, Size: 2232 bytes --]


> This is simply how org-babel-process-params works, it jumps to the
> definition and then executes the source block there (this may be in
> another file even).
>
> 2. The evaluation of header arguments assumes emacs-lisp as a language.
>

Yes, if one wants to execute a language other than Emacs-Lisp, then they
should use a full fledged code block and pass a reference to that code
block into the header argument.

>
> These two combined make it somewhat difficult to use properties to
> control the behaviour of LOB calls and understand what is happening and
> why.  A workaround is to beam the source to the place of call via noweb
> syntax.

This seem a little Rube Goldberg'ish to me.

> The first point could perhaps be addressed in a cleaner way by using
> org-babel-current-src-block-location when calling org-entry-get, but
> I'm not sure yet if it is always correctly set.

I think the best way to handle the first issue would be to use the
recently introduced `org-babel-current-src-block-location' variable, and
jump back to that location when evaluation header arguments.

> Another thorny question is how to deal with another layer of calls
> that might evaluate properties again.

If this is something we need to support, then we would want to turn the
`org-babel-current-src-block-location' variable into a list onto which
we push and pop locations.  Presumably it would then be possible to
evaluate each header argument at the correct location.

> A last option would be to introduce another header argument that can
> be used to inject the properties into the argument list of the call
> and, if set, would suppress any property evaluation in downstream
> calls.
>

I'm not sure I fully understand this solution.

>
> For the second, I think that "lob" should be treated as a language for
> the purpose of anything *-default-header-args* so these settings can be
> independently controlled.
>

I don't know what this means.  I'm either mis-understanding your second
issue, or I strongly disagree with it.  I do not think it should be
possible to embed arbitrary language source code into header arguments.

Cheers,

>
>
> Thoughts, comments?
>
>
> Regards,
> Achim.

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

  parent reply	other threads:[~2013-06-20 16:29 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  9:37 :session question Andreas Röhler
2013-03-25 23:58 ` Michael Gauland
2013-03-26  0:46   ` Eric Schulte
2013-03-26  8:37     ` Andreas Röhler
2013-03-26  9:12     ` Rainer M Krug
2013-03-26  9:23       ` Andreas Leha
2013-03-26 12:37         ` Eric Schulte
2013-03-26 12:44           ` Andreas Leha
2013-03-26 12:55           ` Achim Gratz
2013-03-26 15:31             ` Eric Schulte
2013-03-27  8:01               ` :session question - header argument setting Rainer M Krug
2013-03-27  8:35                 ` Sebastien Vauban
2013-03-27  8:52               ` :session question Andreas Röhler
2013-03-27  9:27                 ` Andreas Leha
2013-03-27 11:37                   ` Andreas Röhler
2013-03-27 11:48                     ` Nick Dokos
2013-03-27 12:18                       ` Andreas Röhler
2013-03-27 12:22                         ` Rainer M Krug
2013-03-27 12:47                           ` Andreas Röhler
2013-03-27 12:43                         ` Eric Schulte
2013-03-27 13:26                           ` Andreas Röhler
2013-03-27 13:29                           ` Andreas Leha
2013-03-27 15:47                             ` Eric Schulte
2013-03-27 20:20                               ` Andreas Leha
2013-03-27 20:35                                 ` Eric Schulte
2013-03-28 10:25                                   ` Andreas Leha
2013-03-28 13:06                                     ` John Hendy
2013-03-28 19:35                                       ` :session question - a simple PATCH Andreas Leha
2013-03-29  9:59                                         ` Achim Gratz
2013-03-29 14:38                                           ` Eric Schulte
2013-03-28 13:22                                   ` :session question John Hendy
2013-03-27 20:59                                 ` Andreas Röhler
2013-03-27 11:19               ` Andreas Leha
2013-04-28 15:46               ` Achim Gratz
2013-05-01 17:18                 ` Eric Schulte
2013-05-01 17:36                   ` Achim Gratz
2013-05-09 18:52                   ` Achim Gratz
2013-06-07 16:15                     ` Achim Gratz
2013-06-07 19:07                       ` :session question -- and changes to #+Property: syntax Eric Schulte
2013-06-07 19:49                         ` Achim Gratz
2013-06-07 20:22                           ` Andreas Leha
2013-06-10  8:16                             ` Rainer M Krug
2013-06-08  7:47                         ` Achim Gratz
2013-06-08 18:08                           ` Eric Schulte
2013-06-08 20:48                             ` Achim Gratz
2013-06-10  8:21                               ` Rainer M Krug
2013-06-10 19:16                                 ` Achim Gratz
2013-06-18 20:41                         ` Achim Gratz
2013-06-19 10:10                           ` Michael Brand
2013-06-20 16:27                           ` Eric Schulte [this message]
2013-06-20 17:47                             ` Achim Gratz
2013-06-20 18:31                               ` Eric Schulte
2013-06-20 19:14                                 ` Achim Gratz
2013-06-20 19:28                                   ` Eric Schulte
2013-06-23 17:50                                   ` Achim Gratz
2013-06-25 14:20                                     ` Eric Schulte
2013-06-25 18:28                                       ` Achim Gratz
2013-06-10  8:14                       ` :session question Rainer M Krug
2013-06-10  8:12                   ` Rainer M Krug
2013-03-27  8:26           ` Andreas Röhler
2013-03-26  6:41   ` Andreas Röhler

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=87ehbwsq5v.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=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).