From: Vladimir Lomov <firstname.lastname@example.org>
To: Jacopo De Simoi <email@example.com>
Cc: Greg Minshall <firstname.lastname@example.org>, email@example.com
Subject: Re: [PATCH] Allow tangling to a list of files
Date: Tue, 6 Jul 2021 14:11:09 +0800 [thread overview]
Message-ID: <YOPz/aBX00yTqhdr@smoon.bkoty.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
** Jacopo De Simoi via General discussions about Org-mode.
<firstname.lastname@example.org> [2021-07-06 01:09:30 -0400]:
> Hi Greg,
> thanks for your comments!
> On Tuesday, July 6, 2021 12:43:54 AM EDT Greg Minshall wrote:
>> hi, Jacopo,
>> i'm not convinced this is needed over and above your old "solution" of
>> using <<noweb>> witn N-different source blocks, each :tangle'ing to a
>> different file.
> To be honest I never quite managed to get it work... =)
> My point here is to be able to have one org file tangle'ing to several,
> slightly different outputs. Ideally I want to use one readable literate config
> for all my machines; the config can then be published (or exported) to html
I do the same with 'noweb' feature.
> Say I want to create an org file to tangle .tmux.conf (or .zshrc) for different
> machines; then most of the conf file would be the same (and each such block
> would be tangled to all files) whereas some specifics could be tangled to
> corresponding files only (e.g. ALIASes or EDITORs)
How this could be solved by your approach by tangling to several files? They
will be identical!
> Even if a solution using noweb could work, I find being able to tangle to a
> list of files more readable and elegant.
Could you explain this a bit more? How you will see that (assuming you have
exported Org to HTML) this goes into different files? Again, if you tangle to
several files they content will be the same! Then why you need different
> Especially when exporting the org in an external format,
> I think the noweb solution would look like a hack,
IMHO, yes, this is a hack and the "standard" way. I would suggest to read
again Org manual concerning "Literate programming".
> whereas a solution with tangle-to-list would be much easier to parse.
How that? You will tangle source block to several files, they content will be
identical! Or you suggesting to add some syntax for source block indicating to
which file to tangle that code snippet?
I would recommend you to describe your needs and how you do things right now.
WBR, Vladimir Lomov
When a camel flies, no one laughs if it doesn't get very far!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-07-06 6:11 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 [this message]
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
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).