emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: briangpowell <briangpowellms@gmail.com>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: literate programming, development log -- ideas?
Date: Mon, 7 Jun 2021 13:59:17 -0400	[thread overview]
Message-ID: <CAFm0skGY-AmeSS_WOOnOncVAJz7r3qvBttV=uBY2QH0VRQXOqA@mail.gmail.com> (raw)
In-Reply-To: <87bl8h7pcl.fsf@web.de>

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

* Donald Knuth created much for us, including TeX and a Literate
Programming system called CWeb which helped to make C code documented in
what he envisioned for Literate Programming

** A more generalized system that is based on CWeb is NoWeb--useful not
just for C/C++ code but for every language: Recommend using NoWeb for
Literate Programming: "NoWeb — A Simple, Extensible Tool for Literate
Programming":

https://www.cs.tufts.edu/~nr/noweb/

"As of 28 June 2018, the current supported version is version 2.12."
{Author recommends against NOWEB 3.x}





On Mon, Jun 7, 2021 at 9:54 AM Dr. Arne Babenhauserheide <arne_bab@web.de>
wrote:

>
> Greg Minshall <minshall@umich.edu> writes:
> > but i also feel a need for something that might be called a lab
> > notebook, a development log, of ideas, including dead ends, i pursue
> > during the development process, with links, etc..  but, i'm not really
> > sure how to structure this bit, how to integrate it in the rest of the
> > .org file -- i.e., as a separate heading, or related to the code section
> > that (originally) was under development when the notes were created.
> > or...?  etc.
>
> I just add more sections/headings, sometimes tagged as :noexport:
>
> If need be, I add code-snippets with examples there.
>
> I feel that that’s the simplest way to do it.
>
> Best wishes,
> Arne
> --
> Unpolitisch sein
> heißt politisch sein
> ohne es zu merken
>

[-- Attachment #2: Type: text/html, Size: 2062 bytes --]

  reply	other threads:[~2021-06-07 18:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 11:43 literate programming, development log -- ideas? Greg Minshall
2021-06-07 12:00 ` Juan Manuel Macías
2021-06-08 17:15   ` literate programming, development log -- ideas? (ominbus reply) Greg Minshall
2021-06-08 17:21     ` Samuel Banya
2021-06-09  8:59       ` Eric S Fraga
2021-06-09 22:21         ` Dr. Arne Babenhauserheide
2021-06-10 22:07           ` Samuel Wales
2021-06-11  0:13             ` Samuel Banya
2021-06-11 14:30               ` Juan Manuel Macías
2021-06-11 15:02                 ` Samuel Banya
2021-06-09 14:52       ` Maxim Nikulin
2021-06-10 13:28         ` Greg Minshall
2021-06-11 19:51       ` Christian Barthel
2021-06-13  0:46       ` Tim Cross
2021-06-13 15:48         ` Samuel Banya
2021-06-13 23:13           ` Tim Cross
2021-06-09  8:57     ` Eric S Fraga
2021-06-13  0:31       ` Tim Cross
2021-06-13  4:27         ` Greg Minshall
2021-06-13  7:29           ` Tim Cross
2021-06-14  6:14             ` Greg Minshall
2021-06-07 12:08 ` literate programming, development log -- ideas? Eric S Fraga
2021-06-13  0:24   ` Tim Cross
2021-06-13 15:44     ` Samuel Banya
2021-06-14 12:57       ` Greg Minshall
2021-06-07 13:53 ` Dr. Arne Babenhauserheide
2021-06-07 17:59   ` briangpowell [this message]
2021-06-07 23:17     ` Dr. Arne Babenhauserheide
2021-06-08  2:06       ` Samuel Banya
2021-06-08  3:23         ` Greg Minshall
2021-06-08  3:31           ` Samuel Banya
2021-06-08  6:15             ` Greg Minshall
2021-06-08 16:59     ` Greg Minshall
2021-06-07 19:19 ` Jack Kamm

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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='CAFm0skGY-AmeSS_WOOnOncVAJz7r3qvBttV=uBY2QH0VRQXOqA@mail.gmail.com' \
    --to=briangpowellms@gmail.com \
    --cc=arne_bab@web.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).