From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id SAb2FW+JxWDZAgAAgWs5BA (envelope-from ) for ; Sun, 13 Jun 2021 06:28:31 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id aKtEEW+JxWA8WwAAbx9fmQ (envelope-from ) for ; Sun, 13 Jun 2021 04:28:31 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 6D26F2467C for ; Sun, 13 Jun 2021 06:28:30 +0200 (CEST) Received: from localhost ([::1]:42896 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lsHjZ-00078P-5f for larch@yhetil.org; Sun, 13 Jun 2021 00:28:29 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:36896) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lsHiz-00078D-1C for emacs-orgmode@gnu.org; Sun, 13 Jun 2021 00:27:53 -0400 Received: from relay-egress-host.us-east-2.a.mail.umich.edu ([18.217.159.240]:43492 helo=driven-mabon.relay-egress.a.mail.umich.edu) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lsHix-0001KM-4i for emacs-orgmode@gnu.org; Sun, 13 Jun 2021 00:27:52 -0400 Received: from nice-yacaruna.authn-relay.a.mail.umich.edu (ip-10-0-72-32.us-east-2.compute.internal [10.0.72.32]) by driven-mabon.relay-egress.a.mail.umich.edu with ESMTPS id 60C58942.A76A2.64E3CEE9.3282512; Sun, 13 Jun 2021 00:27:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=relay-2018-08-29; t=1623558466; bh=pzjoDzl1WxFF9H357qzCpA4CR6xwRiDyzhzX2vRxc5s=; h=From:To:cc:Subject:In-reply-to:Date; b=nekqoCNGBLPrSH9tpX4GO/lKS2TuhLGnV8UDKoCVRBT/33fsVVqxj5MWQ8ritXdT8 eTcDRh1R9uToK9zZG5ATRAAVYGh72aTp94OUf3o0OrPpwup+KRK+zsSM+QztcTqGAp TQU0ex9I5mI9C2u8G6ICpcc7HJtYKXZfES4XxrmEOC32dUktJsI3MC8+v3TshMnm68 X9TzvjbMrlFuAGV79jojaLGflL2hgwCW0b8qFR7LqPLCBle5x6yjICTRj30ErGuKfx Wg4AbGtFwCV40QpupeEUwMziP0jTsFYy6awsfzaEbR7vdvC6Y3+78dmS4Mbr9ThNB/ lj2j3lIHV3CYA== Received: from localhost (Mismatch [95.14.70.92]) by nice-yacaruna.authn-relay.a.mail.umich.edu with ESMTPSA id 60C58941.1D77B.7F67635C.12556; Sun, 13 Jun 2021 00:27:45 -0400 From: Greg Minshall To: Tim Cross Subject: Re: literate programming, development log -- ideas? (ominbus reply) In-reply-to: Your message of "Sun, 13 Jun 2021 10:31:31 +1000." <87r1h6fv72.fsf@gmail.com> X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 27.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1122818.1623558460.1@apollo2.minshall.org> Date: Sun, 13 Jun 2021 07:27:40 +0300 Message-ID: <1122819.1623558460@apollo2.minshall.org> Received-SPF: pass client-ip=18.217.159.240; envelope-from=minshall@umich.edu; helo=driven-mabon.relay-egress.a.mail.umich.edu X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1623558511; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=pzjoDzl1WxFF9H357qzCpA4CR6xwRiDyzhzX2vRxc5s=; b=W6hniuUCYccx3B5S7PMH+ti2gA4EuMdSXqK0bp3kAPob9qt+L7HuVJUauTkiWPeXE30ukN etvTJg5jdZ4f/VoiOdp765Qi6gOhLabOyGt7elU525//uKQsrEWyXCC1LcaJ/QVuzetY3M vF2IEfAaJ1YXfJUfmNw/BffFOR84ew8L1DQWI0wCvEIkOQUvvnzbENv/bcgAFycrBWFtWh mHOsVm5p0HlANcnPZidZwUwTLiBB4TM+7zYppdtFQG8MCNZxFK5Sz1iR2fHdaQzNRVO75b ui2goQ54gZ+hblF1FHhANtROksvH3weB8UNJ3FBO1ejTk9LQ2Y3QhDzHnIehPw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1623558511; a=rsa-sha256; cv=none; b=f7kIydM8pw0vo8jeSC0P/vFC5H+Xj6o+Kg1y/gZ3AgTpcpvkEKYChyra9obYfeS6G5l2l0 BGn1nZhj1UJhKP6FI4bgstugFMIqSNFkqBQPu76TzK2ujHVcltvWxzep9UFB6YHLy3s1s0 hlc4vjZcGkuCAQx7fylinJrOqw5x6ngi0yhd++Uf6b7GS9bJucgd8RZ7jDW10HYjKFgL4z wMac5SshV0cjKaXqRAubbBdCofwRF2hOk4mmD2GY4YrezOqGTuHnDBM6cpI2BLfwaD3O0Z pheVn/3XVxVeVe1LfeEOwufJW5LNmf9s7WLYOugaxoS3JvVmI/kB067Cj99j1Q== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=umich.edu header.s=relay-2018-08-29 header.b=nekqoCNG; dmarc=pass (policy=none) header.from=umich.edu; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Spam-Score: -1.63 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=umich.edu header.s=relay-2018-08-29 header.b=nekqoCNG; dmarc=pass (policy=none) header.from=umich.edu; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 6D26F2467C X-Spam-Score: -1.63 X-Migadu-Scanner: scn1.migadu.com X-TUID: oc+9a/MQfOpV Tim, thanks for your comments. > A lot depends on whether what you want is an org file which documents > the current state of play or one which is more similar to a lab book > which contains a more chronological type evolution of ideas and > experiments. I often setup completely separate org 'projects' which will > consist of multiple org files and will move things between different > files as the project evolves. In some extreme cases, I may even have > multiple git branches and will often use git tags to mark specific > 'milestones'. > > How I decide whether to use a date tree with notes, branches, tags, > archive sections/files, separate org files etc is typically determined > by how likely I might be to want to review or go back through previous > work/experiments/decisions. Working this out can take a bit of time and > experimentation, but in general, I rarely need to checkout old versions > or even open archive trees/files. I do have a journal file for each > major project which has lots of ideas, random thoughts and even small > experiments (with source blokcs) and I tend ot have a large 'reference' > file which contains notes and links to external references and then a > 'main' org file, which reflects the current state. my current curiosity is in how to integrate lab book, brain storming, functionality into my projects. it seems as if, in an extreme case, you might possibly have - a lab book sort of file (i.e., date order, minimal "going back and correcting entries") - a journal file, unstructured, not-infrequently updated, notes, URLs, etc. - the "main" org file -- that which "ships". - an archive file (one per each of the other?) for any given project, is the evolution from =foo.org= to this larger number sort of organic, in the sense that you start with one file, then, at some point, say, "okay, i need to put these bits in a new journal file"? and, trying to leverage the brain cells of others, have you tended to settle on any sort of consistent naming scheme for the different files? =-log=, =-notes=, etc.? i suspect that if my brain were more git-shaped, i'd find the idea of separate files easier. i.e., my instinct is to think of each of these files as having a version-path independent of the others. rather than the git-view, which is that the version-path is the commit-path, and each commit includes the (mostly-temporally) related versions of each of the files. more [C-x v d], less [C-x v v]. again, thanks! Greg