From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Difference :header-args: and :header-args+:?
Date: Mon, 08 Sep 2014 16:17:33 +0200 [thread overview]
Message-ID: <87wq9e9oxu.fsf@Rainer.invalid> (raw)
In-Reply-To: m2y4ty1q48.fsf@krugs.de
Rainer M Krug writes:
> Aaron Ecay <aaronecay@gmail.com> writes:
>>> I have a question concerning the property :header-args:. In addition
>>> to :header-args: there is also :header-args+:.
Since essentially you're asking about property syntax, please read the
corresponding chapter of the manual.
>>> 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?
If you do that at the same level (old-non-lang-specific,
non-lang-specific, lang-specific) then yes.
>>> 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?
You can only override a header argument, not change it. Again, if you
do this at the same level and there are other header arguments at that
level, then the + variant is what you want.
>> Are you aware that you can set individual header args as properties?
>> Something like (at the file level):
Are you aware that this doesn't quite do what you think it does, some of
the time, when things become more complex than your example?
> 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?
If you maybe had an example of what you're trying to do instead of
asking stuff about things you don't want to do? Otherwise, have a look
at
<orgmode.git>/testing/examples/ob-header-arg-defaults.org
and adapt to your needs.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
prev parent reply other threads:[~2014-09-08 14:18 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
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 [this message]
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=87wq9e9oxu.fsf@Rainer.invalid \
--to=stromeko@nexgo.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).