From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Greg Minshall <minshall@umich.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: literate programming, development log -- ideas?
Date: Mon, 07 Jun 2021 13:08:08 +0100 [thread overview]
Message-ID: <874ke9513r.fsf@ucl.ac.uk> (raw)
In-Reply-To: <517779.1623066216@apollo2.minshall.org> (Greg Minshall's message of "Mon, 07 Jun 2021 14:43:36 +0300")
On Monday, 7 Jun 2021 at 14:43, Greg Minshall wrote:
> i write most of my code in a (per-project) .org file, which is typically
> tangled into source or script files.
I do the same.
> i'm wondering if people do this, especially the development log, and if
> there are any hints or practices people might feel would be of interest
> to share.
I use version control for this aspect, liberally adding/deleting
text/code and relying on the version control system to keep the log for
me. I used to try to keep the log, as you call it, within the org file
but that seemed eventually to be both difficult and pointless when there
are decent version control tools out there.
I use src mostly [1] when everything is going to be in one file.
The "current" version of the document will have the code and results
that match the text.
YMMV, of course.
HTH,
eric
Footnotes:
[1] https://gitlab.com/esr/src
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-549-ga0a87d
next prev parent reply other threads:[~2021-06-07 12:13 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 ` Eric S Fraga [this message]
2021-06-13 0:24 ` literate programming, development log -- ideas? 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
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=874ke9513r.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=minshall@umich.edu \
/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).