From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joost Kremers Subject: Re: :tangle header argument not picked up in #+PROPERTY line or :PROPERTIES: block Date: Tue, 31 Mar 2020 00:23:53 +0200 Message-ID: <874ku57aol.fsf@fastmail.fm> References: <87imiof8d3.fsf@fastmail.fm> <77D76CC7-D45E-40A4-9D67-97057256B1E5@ucsd.edu> <878sji2a2i.fsf@fastmail.fm> <63056638-1FBC-495A-BAD0-31ACC44EEFBC@health.ucsd.edu> <877dz2et7r.fsf@fastmail.fm> <87lfnizsus.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; format=flowed Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:51627) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJ2p9-0001aw-L7 for emacs-orgmode@gnu.org; Mon, 30 Mar 2020 18:24:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jJ2p8-00027x-M1 for emacs-orgmode@gnu.org; Mon, 30 Mar 2020 18:24:03 -0400 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:51023) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jJ2p8-00024u-Ad for emacs-orgmode@gnu.org; Mon, 30 Mar 2020 18:24:02 -0400 In-reply-to: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org Sender: "Emacs-orgmode" To: Ken Mankoff Cc: "Berry, Charles" , emacs-orgmode@gnu.org 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