emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Berry, Charles" via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	Ken Mankoff <mankoff@gmail.com>
Subject: Re: :tangle header argument not picked up in #+PROPERTY line or :PROPERTIES: block
Date: Tue, 31 Mar 2020 01:08:38 +0000	[thread overview]
Message-ID: <3174B607-443C-4920-AC76-597183D019C9@health.ucsd.edu> (raw)
In-Reply-To: <874ku57aol.fsf@fastmail.fm>



> On Mar 30, 2020, at 3:23 PM, Joost Kremers <joostkremers@fastmail.fm> wrote:
> 

[stuff deleted]

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


Not so.

`org-babel-view-src-block-info' (C-c C-v C-i with point in the src block below) reports

,----
| Lang: python
| Properties:
| 	:header-args 	nil
| 	:header-args:python 	:session py1 :results function :tangle out1.py
| Header Arguments:
| 	:cache		no
| 	:exports	code
| 	:hlines		no
| 	:noweb		no
| 	:results	function replace
| 	:session	py1
| 	:tangle		out1.py
`----

> 
> 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:
> ```

  reply	other threads:[~2020-03-31  1:08 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
2020-03-31  1:08               ` Berry, Charles via General discussions about Org-mode. [this message]
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=3174B607-443C-4920-AC76-597183D019C9@health.ucsd.edu \
    --to=emacs-orgmode@gnu.org \
    --cc=ccberry@health.ucsd.edu \
    --cc=joostkremers@fastmail.fm \
    --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
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).