From: Aaron Ecay <aaronecay@gmail.com>
To: Rainer M Krug <Rainer@krugs.de>, emacs-orgmode@gnu.org
Subject: Re: Difference :header-args: and :header-args+:?
Date: Fri, 05 Sep 2014 21:18:55 -0400 [thread overview]
Message-ID: <87vbp1r1fk.fsf@gmail.com> (raw)
In-Reply-To: <m2y4ty1q48.fsf@krugs.de>
Hi Rainer,
2014ko irailak 5an, Rainer M Krug-ek idatzi zuen:
>
> Absolutely - but this has been (unfortunately!!!!!!!) be deprecated:
>
> Quoted from the manual [1] :
>
> ,----
> | [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.
> `----
>
> I was using this deprecated behavior and I was *very* happy with it, but
> I am trying to adjust to the new syntax.
>
> So how can I use the new syntax?
Eric Schulte has said <http://mid.gmane.org/87wqce0w9n.fsf@gmail.com>
that the deprecation of this feature is “premature”. I didn’t 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’t help more. Maybe Eric or Achim (who introduced the deprecation)
will comment.
--
Aaron Ecay
next prev parent reply other threads:[~2014-09-06 1:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 10:52 Difference :header-args: and :header-args+:? Rainer M Krug
2014-09-04 16:36 ` Aaron Ecay
2014-09-05 7:30 ` Rainer M Krug
2014-09-06 1:18 ` Aaron Ecay [this message]
2014-09-08 10:36 ` Rainer M Krug
2014-09-08 14:27 ` Achim Gratz
2014-09-08 22:05 ` Aaron Ecay
2014-09-09 8:20 ` Rainer M Krug
2014-09-09 13:57 ` Achim Gratz
2014-09-09 19:19 ` Rainer M Krug
2014-09-09 13:40 ` Achim Gratz
2014-09-18 1:37 ` Aaron Ecay
2014-09-09 7:40 ` Rainer M Krug
2014-09-09 7:56 ` Rainer M Krug
2014-09-08 14:17 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbp1r1fk.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=Rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).