From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: Re: link abbreviation with multiple params, e. g. for geo locations Date: Fri, 7 Jun 2013 16:53:10 +0200 Message-ID: References: <87a9n35g25.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51809) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uky2T-0004qq-Ug for emacs-orgmode@gnu.org; Fri, 07 Jun 2013 10:53:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uky2S-0005yW-J5 for emacs-orgmode@gnu.org; Fri, 07 Jun 2013 10:53:13 -0400 Received: from mail-la0-x235.google.com ([2a00:1450:4010:c03::235]:54248) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uky2S-0005yO-Cj for emacs-orgmode@gnu.org; Fri, 07 Jun 2013 10:53:12 -0400 Received: by mail-la0-f53.google.com with SMTP id fs12so2326964lab.12 for ; Fri, 07 Jun 2013 07:53:10 -0700 (PDT) In-Reply-To: <87a9n35g25.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Schulte Cc: Org Mode Hi Eric Thank you for looking into this. On Thu, Jun 6, 2013 at 7:01 PM, Eric Schulte wrote: > Is the only requirement that > the point from which a code block was called be accessible to the > emacs-lisp code executed within that code block? Yes. > If so then there should be no need for additional development. The > following already works thanks to some very recently applied changes. Is release_8.0.3-207-g5dc5143 the change you mention?: commit 5dc5143578a2759611a5856de9bf9d1c7eba9283 Author: Eric Schulte Date: Thu Jun 6 10:59:27 2013 -0600 inline sets org-babel-current-exec-src-block-head In this commit I see two issues which my patch does not have: 1) The variable name org-babel-current-exec-src-block-head is the same as for a different meaning (source block head) and purpose introduced in release_8.0.3-202-gf301bbc commit f301bbcc862c2acc61749bc1e24895bf69cd4d06 Author: Vitalie Spinu Date: Thu Jun 6 12:04:02 2013 +0200 make src block location available to execution backends but in release_8.0.3-207-g5dc5143 the same name is used for the point-marker of "call_func" which is misleading. In my patch I named the variable "loc" for Location Of Call. And I chose intentionally a name as short as possible to keep the "#+HEADER:" lines not getting too wide, see e. g. the ERT in my patch. 2) Export is not supported ("C-c C-c" works as expected). Just today I saw a possible improvement for my patch: For a more general usage of "loc" than only for org-entry-get it would be better if "loc" in export would not contain the location of the entry start but the exact location of possibly more than one call within the same entry. For "C-c C-c" this is already the case. Since I don't know how to resolve this I would let it as is for now unless there is a suggestion. I would like to provide a new patch if I know what else should be improved. Michael