emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Joost Kremers <joostkremers@fastmail.fm>
To: "Berry, Charles" <ccberry@health.ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: :tangle header argument not picked up in #+PROPERTY line or :PROPERTIES: block
Date: Sun, 29 Mar 2020 22:13:57 +0200	[thread overview]
Message-ID: <878sji2a2i.fsf@fastmail.fm> (raw)
In-Reply-To: <77D76CC7-D45E-40A4-9D67-97057256B1E5@ucsd.edu>

On Sun, Mar 29 2020, Berry, Charles via General discussions about 
Org-mode. wrote:
>> On Mar 28, 2020, at 3:00 PM, Joost Kremers 
>> <joostkremers@fastmail.fm> wrote:
>> Is this expected behaviour? Am I doing something wrong?
> IIUC what you did, then yes and yes.
> This is the accepted idiom:
> #+PROPERTY: header-args :tangle yes

I have tried:

  #+PROPERTY: header-args:python :tangle yes :dir 

which AFAICT is the syntax shown in the info node you mentioned. I 
have also tried a file name instead of =yes=, both with and 
without quotes, but it doesn't work.

What I really want is to have a property block with the =:tangle= 
arg under each top-level header, like so:

  :header-args:python: :tangle out1.py

because I want the code below each top-level header to be tangled 
to a separate file. Again, AFAICT this is the syntax described in 
the info manual.

Hmm, experimenting a bit more I find that if I leave out the 
=python= part, it works:

  :header-args: :tangle out1.py

But the info manual gives this example:

  :header-args:clojure:    :session *clojure-1*

The same is true for the #+PROPERTY block at the top of the file: 
leave out the =python=, it works. Isn't it possible to restrict 
tangling to source blocks of a particular language? (Or, more 
specifically what I want: to specify different tangling targets 
for different language? I wanted to have both python and bash code 
blocks under one header and have them tangled to different 


Joost Kremers
Life has its moments

  reply	other threads:[~2020-03-29 20:14 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 [this message]
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.
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:

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


* 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


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