From: "Berry, Charles" via "General discussions about Org-mode." <firstname.lastname@example.org>
To: Tim Cross <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>,
Marko Schuetz-Schmuck <MarkoSchuetz@web.de>
Subject: Re: A requires/provides approach to linking source code blocks
Date: Fri, 9 Jul 2021 20:27:36 +0000 [thread overview]
Message-ID: <4D908526-FD29-4852-9B9F-260A405518B1@health.ucsd.edu> (raw)
> On Jul 8, 2021, at 12:32 PM, Tim Cross <firstname.lastname@example.org> wrote:
> My concern here is with the additional complexity. This is already a
> somewhat complex aspect of org mode and the behaviour you describe can
> effectively be done using noweb, although as you say, not as
> declarative in style.
This (and the rest of what you said) is very well taken.
I share your concern that adding features to an already rich feature suite will make babel very difficult to penetrate.
p.s. Extracting code from src blocks need not depend on `org-babel-tangle' and friends. Custom exporters have to potential to render code using attribute keys and other export features. And such exporters have the virtue of not adding complexity to the org code base.
next prev parent reply other threads:[~2021-07-09 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 16:24 A requires/provides approach to linking source code blocks Marko Schuetz-Schmuck
2021-07-08 19:32 ` Tim Cross
2021-07-09 8:22 ` Slowing down new features Timothy
2021-07-09 13:38 ` A requires/provides approach to linking source code blocks Maxim Nikulin
2021-07-09 20:27 ` Berry, Charles via General discussions about Org-mode. [this message]
2021-07-09 7:29 ` Stefan Nobis
2021-07-09 17:00 autofrettage
2021-07-12 9:55 ` Alexander Adolf
2021-07-13 19:18 ` Tom Gillespie
2021-07-13 19:42 ` George Mauer
2021-07-14 0:44 ` Tim Cross
2021-07-14 1:53 ` Samuel Wales
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).