emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: emacs-orgmode@gnu.org
Cc: Aaron Ecay <aaronecay@gmail.com>
Subject: Re: Difference :header-args: and :header-args+:?
Date: Fri, 05 Sep 2014 09:30:15 +0200	[thread overview]
Message-ID: <m2y4ty1q48.fsf@krugs.de> (raw)
In-Reply-To: <877g1j1gwx.fsf@gmail.com> (Aaron Ecay's message of "Thu, 04 Sep 2014 12:36:46 -0400")

[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]

Aaron Ecay <aaronecay@gmail.com> writes:

> Hi Rainer,
>
> 2014ko irailak 4an, Rainer M Krug-ek idatzi zuen:
>> 
>> Hi
>> 
>> I have a question concerning the property :header-args:. In addition
>> to :header-args: there is also :header-args+:.
>> 
>> 
>> 1) If I set some properties globally and in a subtree I want to *add* a
>> *new* header argument - do I have to use the + or not?
>> 
>> 2) If I set some properties globally and in a subtree I want to *change*
>> a *single* header argument which *was set globally* - do I have to use
>> the + or not?
>
> Are you aware that you can set individual header args as properties?
> Something like (at the file level):
>
> #+property: session *foo*
>
> or (at the subtree level):
>
> :PROPERTIES:
> :session: *foo*
> :END:
>
> This will likely be easier than trying to do surgery on the header-args
> property.

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?

Rainer

Footnotes: 
[1]  http://orgmode.org/manual/Header-arguments-in-Org-mode-properties.html#Header-arguments-in-Org-mode-properties

-- 
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982

[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]

  reply	other threads:[~2014-09-05  7:30 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 [this message]
2014-09-06  1:18     ` Aaron Ecay
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=m2y4ty1q48.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=aaronecay@gmail.com \
    --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).