emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marko Schuetz-Schmuck <MarkoSchuetz@web.de>
To: emacs-orgmode@gnu.org
Subject: A requires/provides approach to linking source code blocks
Date: Thu, 08 Jul 2021 12:24:15 -0400	[thread overview]
Message-ID: <87czrsai4w.fsf@tpad-m.i-did-not-set--mail-host-address--so-tickle-me> (raw)

[-- Attachment #1: Type: text/plain, Size: 843 bytes --]

Dear All,

AFAIU in the current support for literate programming I can establish
sequence between blocks by either tangling the entire file whereby the
blocks are written to the source code file in the sequence in which they
appear in the org-mode file or I can name the blocks and use noweb
linking to explicitly state the precise sequence in which the blocks
appear in the source code file.

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.

I'd be interested in feedback on the idea.

Please include my email address in the reply as I am not subscribed to
the list.

Best regards,


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 223 bytes --]

             reply	other threads:[~2021-07-08 17:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08 16:24 Marko Schuetz-Schmuck [this message]
2021-07-08 19:32 ` A requires/provides approach to linking source code blocks 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.
2021-07-09  7:29 ` Stefan Nobis
  -- strict thread matches above, loose matches on Subject: below --
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

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=87czrsai4w.fsf@tpad-m.i-did-not-set--mail-host-address--so-tickle-me \
    --to=markoschuetz@web.de \
    --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).