From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: :session question -- and changes to #+Property: syntax Date: Thu, 20 Jun 2013 13:28:32 -0600 Message-ID: <87y5a4r38f.fsf@gmail.com> References: <51501AF2.1070405@easy-emacs.de> <8738vjugwd.fsf@gmail.com> <51516699.6090604@gmail.com> <87ip4ezf93.fsf@med.uni-goettingen.de> <87fvzi72ve.fsf@gmail.com> <87ip4e5gai.fsf@gmail.com> <87k3nmd5es.fsf@Rainer.invalid> <87sj264o0f.fsf@gmail.com> <87k3n8gf47.fsf@Rainer.invalid> <878v2l7v7s.fsf@Rainer.invalid> <87txl9u4c4.fsf_-_@gmail.com> <87d2rjcfsv.fsf@Rainer.invalid> <87ehbwsq5v.fsf@gmail.com> <874ncsad3p.fsf@Rainer.invalid> <87a9mkskfa.fsf@gmail.com> <87vc588uha.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38735) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpkYA-0007tk-QE for emacs-orgmode@gnu.org; Thu, 20 Jun 2013 15:29:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UpkYA-0007BU-0g for emacs-orgmode@gnu.org; Thu, 20 Jun 2013 15:29:42 -0400 Received: from mail-pa0-x234.google.com ([2607:f8b0:400e:c03::234]:48472) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpkY9-0007BM-RP for emacs-orgmode@gnu.org; Thu, 20 Jun 2013 15:29:41 -0400 Received: by mail-pa0-f52.google.com with SMTP id kq13so6637796pab.39 for ; Thu, 20 Jun 2013 12:29:41 -0700 (PDT) In-Reply-To: <87vc588uha.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 20 Jun 2013 21:14:57 +0200") 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: Achim Gratz Cc: emacs-orgmode@gnu.org >> Hopefully the simpler solution which uses the existing value of >> `org-babel-current-src-block-location' will prove sufficient (once >> someone implements it that is...). > > I'll implement it and see if this seems more useful than the current > behaviour. If it is, then we'll have to decide if that new behaviour > replaces the old one or yet another header argument or option switches > between old and new. I guess it could be arranged so that the old-style > properties kept the old behaviour and the new-style properties followed > the new=E2=80=A6 > Introducing another header argument controlling this setting would add too much complexity. I think we either stick with the existing behavior or (preferably) change the default behavior. Thanks for taking these on! > > > Regards, > Achim. --=20 Eric Schulte http://cs.unm.edu/~eschulte