From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id bbQgN6oGvmBqEwEAgWs5BA (envelope-from ) for ; Mon, 07 Jun 2021 13:44:42 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id qOTNMaoGvmBXCAAAB5/wlQ (envelope-from ) for ; Mon, 07 Jun 2021 11:44:42 +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 29ED917DB7 for ; Mon, 7 Jun 2021 13:44:42 +0200 (CEST) Received: from localhost ([::1]:58060 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lqDgO-00064T-Ij for larch@yhetil.org; Mon, 07 Jun 2021 07:44:40 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:55312) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lqDfX-00064E-TJ for emacs-orgmode@gnu.org; Mon, 07 Jun 2021 07:43:48 -0400 Received: from relay-egress-host.us-east-2.a.mail.umich.edu ([13.59.128.245]:40932 helo=lepid-pryderi.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 1lqDfS-00031p-IB for emacs-orgmode@gnu.org; Mon, 07 Jun 2021 07:43:47 -0400 Received: from quixotic-jackalope.authn-relay.a.mail.umich.edu (ip-10-0-74-19.us-east-2.compute.internal [10.0.74.19]) by lepid-pryderi.relay-egress.a.mail.umich.edu with ESMTPS id 60BE066D.4F04D.23217DE9.168144; Mon, 07 Jun 2021 07:43:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=relay-2018-08-29; t=1623066221; bh=oFB+TE3Q+71bmFGh1p+mYlFFdF2TsamEqLoUuD1W/k4=; h=From:To:Subject:Date; b=fvLt5cPyFVFEo+F8H5D7sRr0TJuByExAP5zP0Dvf+TIdqBawzOn2ed6YagdtKb2eL aNEHTccU0jW9TRdDziQY/9rYdfguWVvOx9tiXJK43UV0YXsaywe3QyG4Xcl883IqaM SQlKnRXVHePffTe2bobuEZzGsTHSNY6Llbmds5IPDe7toJPH+SAdif9QmpvEeVBFq9 GydXgKFJPOI2Pn1cW219KmqgE3GzUO+WA+Cqg7eXZTIILkFwragaWWrziVXW4OAUy8 d3tHIOrSBoSAc/Gs39IilhwpKDKcs1NtiZAntRTNFR2h79RV0oNUV9vh8bM996h2zG Fiz5er/yd80Sw== Received: from localhost (Mismatch [88.236.235.126]) by quixotic-jackalope.authn-relay.a.mail.umich.edu with ESMTPSA id 60BE066C.58E1B.11FA9681.1954859; Mon, 07 Jun 2021 07:43:40 -0400 From: Greg Minshall To: emacs-orgmode Subject: literate programming, development log -- ideas? 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: <517778.1623066216.1@apollo2.minshall.org> Date: Mon, 07 Jun 2021 14:43:36 +0300 Message-ID: <517779.1623066216@apollo2.minshall.org> Received-SPF: pass client-ip=13.59.128.245; envelope-from=minshall@umich.edu; helo=lepid-pryderi.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: , 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=1623066282; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=oFB+TE3Q+71bmFGh1p+mYlFFdF2TsamEqLoUuD1W/k4=; b=BHd0/qlPs1rpQOW3WTHbZCgRTVb0tNBzfPbpxcdqjx+Z+7nSqpNWZpZYx11C28LPznwD3E 8CLc23ebJam6vy6YrFrVVn8NLtSiwTP6fGZ2SrjnyYBvNZ9hUJkKyIO6oupSeYF7cFY4gO mDXF53y6I23xZ827QBB00jOkIrdeauAFbh7Y0+EX1Iwz1VMS3bmUFUHIF5+PSVSMcbPjlM 1B6kRHskTy62/JS/DJLt7+vt/FpT6mqAnuL0yGeZiTjn+8GTuFXmNEEmtgQGtf7koCl4AU Z6wvsVLlxMon0hInfIjoUev2/0lz+Z4RtfWIG6BdC5nD/XF+jvp4Zm9sN2+lqQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1623066282; a=rsa-sha256; cv=none; b=pdCJHNj4vriXCUqE7SOuhWi6/QkiGQr9sNuW3+IKP0YQGpOk/DAwQ/HCQW156MUIeL1bJj 6+iKeQZ4X4uXADFo0PuI2k6gouKjZVTPwLrSGGmYMvWL6GwfDK4ykCNfI9G2ppOm38fMEB hznKZbDGEYwqgJLn9RI6r2INLr/l/Brmf3zyXxzD0aM8StPO7wduwHWChiwhxOIMBHCxoh GwIT6ztXqdb4jzYUnRK411CPxIAfpWRc9Qbc5o+dBG3VkGtVxuEJRuHwP1R22cI1vQBbF9 7PPJbradz1pNr+XZCiIBQpLeVmUS301YDOyr8Xb7RetElGkKCiRvcvvhpMY0hQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=umich.edu header.s=relay-2018-08-29 header.b=fvLt5cPy; 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: -0.62 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=umich.edu header.s=relay-2018-08-29 header.b=fvLt5cPy; 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: 29ED917DB7 X-Spam-Score: -0.62 X-Migadu-Scanner: scn1.migadu.com X-TUID: FUKalmeGRqI2 hi, all. i write most of my code in a (per-project) .org file, which is typically tangled into source or script files. i have a question about how people structure their .org files for this sort of use. some of the non-source bits surrounding my source blocks are for "classical" literate programming text, i.e., introductions to sections of code, maybe with links to external pages for libraries or packages i use in the associated code block. 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'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. (sorry for the non-specificness of the question.) cheers, Greg