From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rainer M Krug Subject: Re: Difference :header-args: and :header-args+:? Date: Mon, 08 Sep 2014 12:36:34 +0200 Message-ID: References: <877g1j1gwx.fsf@gmail.com> <87vbp1r1fk.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35970) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XQwJQ-0000Fe-Nf for emacs-orgmode@gnu.org; Mon, 08 Sep 2014 06:36:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XQwJK-0002kG-Dz for emacs-orgmode@gnu.org; Mon, 08 Sep 2014 06:36:44 -0400 Received: from mail-wi0-f170.google.com ([209.85.212.170]:34228) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XQwJK-0002k7-8j for emacs-orgmode@gnu.org; Mon, 08 Sep 2014 06:36:38 -0400 Received: by mail-wi0-f170.google.com with SMTP id cc10so2392607wib.1 for ; Mon, 08 Sep 2014 03:36:37 -0700 (PDT) Received: from Rainers-MacBook-Pro-3.local (arn78-1-88-186-171-7.fbx.proxad.net. [88.186.171.7]) by mx.google.com with ESMTPSA id gl10sm10767331wib.1.2014.09.08.03.36.35 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Sep 2014 03:36:36 -0700 (PDT) In-Reply-To: <87vbp1r1fk.fsf@gmail.com> (Aaron Ecay's message of "Fri, 05 Sep 2014 21:18:55 -0400") 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: emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I would like to ping this question, as it is still bothering me and I could not find any explanation. Thanks, Rainer Aaron Ecay writes: > Hi Rainer, > > 2014ko irailak 5an, Rainer M Krug-ek idatzi zuen: >>=20 >> Absolutely - but this has been (unfortunately!!!!!!!) be deprecated: >>=20 >> Quoted from the manual [1] : >>=20 >> ,---- >> | [1] The deprecated syntax for default header argument properties, using >> | the name of the header argument as a property name directly, evaluates >> | the property as seen by the corresponding source block definition. This >> | behavior has been kept for backwards compatibility. >> `---- >>=20 >> I was using this deprecated behavior and I was *very* happy with it, but >> I am trying to adjust to the new syntax. >>=20 >> So how can I use the new syntax? > > Eric Schulte has said > that the deprecation of this feature is =E2=80=9Cpremature=E2=80=9D. I d= idn=E2=80=99t realize > at the time that the deprecation was also included in the manual rather > than just a code comment. Possibly it should be un-deprecated. > > Certainly I agree that the suggested replacement is less capable. Sorry > I can=E2=80=99t help more. Maybe Eric or Achim (who introduced the depre= cation) > will comment. =2D-=20 Rainer M. Krug email: Rainerkrugsde PGP: 0x0F52F982 --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBAgAGBQJUDYayAAoJENvXNx4PUvmCwXYIALXC+1KzXVBpb/L3F3hHtd/l dgN6PEpq5ZssB5/ZCFFEy8vvjxmfKquib73dboDWXlpzzdUd2bnLY1WNFLuGtzAG ZtcKUY7mbDkOL8IYbT3Hr2Zf09Qkrbhpjr6v9cvJ5pAvAoun0a8VvnRtSi23nycM TxHY/6FLDa/6zejMeOPbPYLwW0d9wJVLQUoyipxA0ocCgS0z6auVlCjLrN3EwScE RRo75IRrIonsVHoZqeT0djBlB0KEEcvoa0Y5KTyltJ63/q7vLlIjVOri82Aaeszk keJvi1PuQ9EdQEVVHBwgKbbta7piyiogImDJUkDQXpARG0V2T7d4HFTJBwxArmA= =BXWS -----END PGP SIGNATURE----- --=-=-=--