emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Joost Kremers <joostkremers@fastmail.fm>
To: Ken Mankoff <mankoff@gmail.com>
Cc: "Berry, Charles" <ccberry@health.ucsd.edu>, emacs-orgmode@gnu.org
Subject: Re: :tangle header argument not picked up in #+PROPERTY line or :PROPERTIES: block
Date: Tue, 31 Mar 2020 00:23:53 +0200	[thread overview]
Message-ID: <874ku57aol.fsf@fastmail.fm> (raw)
In-Reply-To: <CAFdBzEr9aed=mcXpiNnou46tcDFyvT79J2ikFcnehGXksC0+LA@mail.gmail.com>


On Mon, Mar 30 2020, Ken Mankoff wrote:
> Header args overwrite. Change python to python+ to append header 
> args.

Are you sure? That's not documented anywhere I can find and it 
seems to be belied by the fact that if I put the headers in the 
order:

```
:PROPERTIES:
:header-args:python: :tangle out1.py
:header-args:python: :session py1 :results function
:END:
```

everything works as I would expect (the code blocks are tangled to 
a file `out1.py` *and* they are evaluated in a python session 
`py1`), meaning that *all* header args are picked up.

If I reverse the order and add a `+` sign, like so:

```
:PROPERTIES:
:header-args:python+: :session py1 :results function
:header-args:python+: :tangle out1.py
:END:
```

the code does indeed get tangled, but the `:results` header arg 
isn't picked up, because the code block doesn't produce any 
output.

For reference, this is my test file:

```
* Header 1
:PROPERTIES:
:header-args:python+: :session py1 :results function
:header-args:python+: :tangle out1.py
:END:

#+begin_src python
a=1
b=2
c=a+b
return c
#+end_src

#+RESULTS:
```


-- 
Joost Kremers
Life has its moments

next prev parent reply	other threads:[~2020-03-30 22:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28 22:00 :tangle header argument not picked up in #+PROPERTY line or :PROPERTIES: block Joost Kremers
2020-03-29 17:45 ` Berry, Charles via General discussions about Org-mode.
2020-03-29 20:13   ` Joost Kremers
2020-03-29 20:41     ` Berry, Charles via General discussions about Org-mode.
2020-03-29 22:07       ` Joost Kremers
2020-03-29 22:41         ` Joost Kremers
2020-03-29 23:44           ` Ken Mankoff
2020-03-30 22:23             ` Joost Kremers [this message]
2020-03-31  1:08               ` Berry, Charles via General discussions about Org-mode.
2020-03-31 20:04                 ` Joost Kremers
2020-03-31 15:14               ` Ken Mankoff
2020-03-31 19:54                 ` Joost Kremers
  -- strict thread matches above, loose matches on Subject: below --
2020-03-31  1:01 Thomas S. Dye
2020-04-01 19:07 ` Joost Kremers

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=874ku57aol.fsf@fastmail.fm \
    --to=joostkremers@fastmail.fm \
    --cc=ccberry@health.ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=mankoff@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

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).