From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastien Vauban Subject: Re: Discussion request: 15m tangle time, details follow Date: Wed, 18 Jun 2014 10:13:56 +0200 Message-ID: <86mwdaprcr.fsf@somewhere.org> References: <87ppi76irx.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Aaron, Aaron Ecay wrote: > [...] > babel needs to fetch 30 properties per source block. Indeed, this is > marked =E2=80=9Cdeprecated=E2=80=9D in the source, in favor of a system w= here there is > only one header arg. This has been marked deprecated for almost exactly > a year in the code (Achim=E2=80=99s commit 90b16870 of 2013-06-23), but I= don=E2=80=99t > know of any prominent announcement of the deprecation. I neither was aware of such a deprecation. Are you talking of the comment in function `org-babel-params-from-properties' (in ob-core.el)? Thought, I can't parse it yet the way you do -- without understanding much more of that code, as the comments differ in "at point of definition" vs "at point of call": ;; DEPRECATED header arguments specified as separate property at ;; point of definition ;; header arguments specified with the header-args property at ;; point of call What you're talking about is for specifying header arguments in a subtree, anyway always at the same point: > [...] You=E2=80=99d then have to update your file: > > :PROPERTIES: > :exports: none > :tangle: no > :END: > > becomes > > :PROPERTIES: > :header-args: :exports none :tangle no > :END: > > The new system is also a bit inferior, in that it doesn=E2=80=99t allow h= eader > arg inheritance as easily. So with the one-prop-per-arg system the > following works as expected: > > * foo > :PROPERTIES: > :exports: none > :END: > ** bar > :PROPERTIES: > :tangle: no > :END: > > (src block here) > > On the other hand, in the new system there=E2=80=99s no way to specify so= me > header args at foo and some at bar; the lowest header-args property > wins. (At least as far as I can see) Maybe the "+" mechanism for concatenating property strings would help here? Best regards, Seb --=20 Sebastien Vauban