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: Sun, 9 Jun 2013 09:56:22 +0200 Message-ID: References: <87a9n35g25.fsf@gmail.com> <87fvwuuez8.fsf@gmail.com> <87k3m4mozj.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]:44032) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UlaUG-0006sD-FJ for emacs-orgmode@gnu.org; Sun, 09 Jun 2013 03:56:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UlaUC-00060w-TL for emacs-orgmode@gnu.org; Sun, 09 Jun 2013 03:56:28 -0400 Received: from mail-lb0-f173.google.com ([209.85.217.173]:37387) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UlaUC-00060e-Kd for emacs-orgmode@gnu.org; Sun, 09 Jun 2013 03:56:24 -0400 Received: by mail-lb0-f173.google.com with SMTP id v1so578042lbd.32 for ; Sun, 09 Jun 2013 00:56:23 -0700 (PDT) In-Reply-To: <87k3m4mozj.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 On Sat, Jun 8, 2013 at 8:03 PM, Eric Schulte wrote: > I've just pushed up a commit which should fix this problem. The > org-babel-current-exec-src-block-head variable wasn't bound during > export. Confirmed, thanks. In the attached marker_offset.org the evaluation of the variable todo-state-var during export did not work before, now it does. What I do not understand is the behavior of the evaluation of the other variable marker-var. During "C-c C-c" it is like expected with point >= 305 which means within entry "* s". But during export it is far before 305 which confuses me. How can "DONE" instead of nil from the previous entry be assigned to todo-state-var this way and is this "displacement" to be accepted? For me it is enough for now if the marker is just anywhere within the current entry. I do not (yet?) have a use case where I need the marker to be at an individual source block and therefore different when calling a function twice in the same entry as in marker_offset.org with calls "(a)" and "(b)". Michael