From: Maxim Nikulin <firstname.lastname@example.org>
Subject: Re: A requires/provides approach to linking source code blocks
Date: Fri, 9 Jul 2021 20:38:14 +0700 [thread overview]
Message-ID: <email@example.com> (raw)
On 09/07/2021 02:32, Tim Cross wrote:
> Marko Schuetz-Schmuck writes:
>> I would find it useful to have a more declarative way for specifying
>> sequence. I imagine e.g. using "#+REQUIRES:" and "#+PROVIDES:" to
>> capture dependency and then have the exporter compute a sequence
>> satisfying these. I would think that this makes the maintenance of the
>> dependencies more convenient.
> 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.
There was a feature request for dependencies between code blocks to run
them in proper order a half of a year ago.
I think, it is better to try such feature as an extension of org, as a
separate package. I suspect that some non-obvious issue may arise.
Likely, to be convenient, it will be desired to autofill
requires/provides attributes using some tools related to particular
The question is whether org code is organized in such way, so extensions
of this kind are possible without code duplication. Maybe API could be
adjusted. On the other hand, even maintaining of stable semi-internal
API sometimes is significant burden.
P.S. I am reading the mail list through NNTP news.gmain.io. I have
noticed that personal copies sometimes arrives without mail list
address. Sorry if you will have to manually add it to reply.
next prev parent reply other threads:[~2021-07-09 13:39 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 ` Maxim Nikulin [this message]
2021-07-09 20:27 ` A requires/provides approach to linking source code blocks Berry, Charles via General discussions about Org-mode.
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).