From: Jacopo De Simoi <firstname.lastname@example.org>
To: email@example.com, firstname.lastname@example.org
Subject: Re: [PATCH] Allow tangling to a list of files
Date: Wed, 07 Jul 2021 11:05:55 +0000 [thread overview]
Message-ID: <NZf5j4oJ7UP6ZBpTFGscUgaiSgEmeeQpg-jnliRb8qjXdMfViScdLlnX_gOiyBFXoHiZYliHj7n9IPPRQtCKgzRSNegGmXk2m06g8d7Rd4Iemail@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
Thanks for bringing this up
-------- Original Message --------
On Jul. 7, 2021, 02:56, Greg Minshall < firstname.lastname@example.org> wrote:
> I couldn't find in Org manual how tangling should work if there are
> several source code blocks with the same file name for ':tangle'. The
> Org manual section "15.8 Extracting Source Code" is a bit
> obscure. There are these two sentences
i think what Tim answered is correct. but, i believe the "desired"
approach is to put all those blocks to be tangled to the same file under
a headline with a property drawer containing something like:
:header-args+: :tangle "submsim.jl"
i believe this is for performance of tangling, but possibly the
"multiple source blocks to same :tangle'd file" feature may disappear?
Once again, there is a unit test designed to check that different blocks tangling to the same file are concatenated in the right order, this without a common property drawer. Hence I believe this behavior is not accidental, but a wanted feature.
I always understood that this was the expected behavior, to allow descriptions to interleave code in a literate config situation.
However, if the documentation is ambiguous, or lacking, then we should probably make the docs clear, so that this question does not rise again in the future.
[-- Attachment #2: Type: text/html, Size: 1460 bytes --]
next prev parent reply other threads:[~2021-07-07 11:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 18:54 [PATCH] Allow tangling to a list of files Jacopo De Simoi
2021-07-06 2:57 ` Vladimir Lomov
2021-07-06 4:43 ` Greg Minshall
2021-07-06 5:09 ` Jacopo De Simoi via General discussions about Org-mode.
2021-07-06 6:11 ` Vladimir Lomov
2021-07-06 15:24 ` Jacopo De Simoi via General discussions about Org-mode.
2021-07-07 3:27 ` Vladimir Lomov
2021-07-07 4:09 ` Tim Cross
2021-07-07 5:01 ` Jacopo De Simoi
2021-07-07 6:56 ` Greg Minshall
2021-07-07 11:05 ` Jacopo De Simoi [this message]
2021-07-09 12:26 ` Vladimir Lomov
2021-07-09 13:39 ` Jacopo De Simoi
2021-07-09 22:47 ` Tim Cross
2021-07-06 7:30 ` Tim Cross
2021-07-07 23:06 ` Jacopo De Simoi via General discussions about Org-mode.
2021-07-07 23:28 ` Tim Cross
2021-07-08 0:01 ` Jacopo De Simoi
2021-07-08 0:41 ` Tom Gillespie
2021-07-08 16:41 ` Trust me I am a Doctor
2021-07-08 17:42 ` Jacopo De Simoi
[not found] <-0ZoEP_lzUvrnWSq9TwiYHNJ0Spa94xjiTOF0TU8np0pYgHEPx-62_dr5xBMd3VUu7frSRXxiAFje99v2jeaJgemail@example.com>
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 \
* 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).