emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: Alan Schmitt <alan.schmitt@polytechnique.org>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: two sets of default header arguments for one language
Date: Fri, 11 Sep 2015 09:09:01 +0200	[thread overview]
Message-ID: <m2bnd9mnzm.fsf@krugs.de> (raw)
In-Reply-To: <87r3m6q85a.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Thu, 10 Sep 2015 23:25:21 +0200")

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

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Rainer M Krug <r.m.krug@gmail.com> writes:
>
>> Do macros work for properties ? If yes, you could degine two macro,
>> one for each set of properties.
>
> No, they don't.

That's a pity.

It would be really great if one could define different sets of
hearer-args and then, at thr beginning of a code block, simply use:

#+MACRO: forTangle  :tangle ./test.R :export none
#+MACRO: forExecution  :tangle no :export both :session Test14
#+MACRO: forNoSession  :tangle no :export both

#+:header-args {{{forTangle}}}
#+begin_src R :tangle no
  cat(13)
#+end_src

#+:header-args {{{forExecution}}}
#+begin_src R :tangle no
  cat(14)
#+end_src

#+:header-args {{{forNoSession}}}
#+begin_src R :tangle no
  cat(14)
#+end_src


This would make it much easier to work with header-args and solve many
problems which were discussed in earlier threads.

The example might not be the best as it could be implemented by
header-args+ but if the code blocks using the different sets of
header-args are at different locations in the org document, changing
them would be much easier with macro expansion (or similar).

Would it be difficult to include this feature?

Thanks,

Rainer

>
> Regards,

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug

PGP: 0x0F52F982

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 480 bytes --]

  reply	other threads:[~2015-09-11  7:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10 13:54 two sets of default header arguments for one language Alan Schmitt
2015-09-10 21:00 ` Thomas S. Dye
2015-09-11  9:30   ` Alan Schmitt
2015-09-10 21:16 ` Rainer M Krug
2015-09-10 21:25   ` Nicolas Goaziou
2015-09-11  7:09     ` Rainer M Krug [this message]
2015-09-11  9:33       ` Alan Schmitt
2015-09-11 16:27       ` Nicolas Goaziou
2015-09-18 10:17         ` Rainer M Krug
2015-09-10 22:28 ` Charles C. Berry
2015-09-10 22:39   ` Charles C. Berry
2015-09-11  9:36     ` Alan Schmitt
2015-09-14 14:39       ` Alan Schmitt

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=m2bnd9mnzm.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=r.m.krug@gmail.com \
    /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).