From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms1.migadu.com with LMTPS id ILiNK9CoTGYa8QAAqHPOHw:P1 (envelope-from ) for ; Tue, 21 May 2024 15:59:44 +0200 Received: from aspmx1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id ILiNK9CoTGYa8QAAqHPOHw (envelope-from ) for ; Tue, 21 May 2024 15:59:44 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=blackmesatech.com header.s=dreamhost header.b=bBbwWH5v; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=none; arc=pass ("mailchannels.net:s=arc-2022:i=1") ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1716299984; 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: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=8jpSZo1H8yP59JLt2j+2Dxnapwx0peUT3LmSYclFMxg=; b=DVZVde76wLvSXk6a4DvQ18hDs+B80fdYwPn52G+xQFqM9Mf7KU0j/yYLHIIJ4/vKwtd0XY LZzlKkOqahFZuYqVCl6Ud7bvM5GGDzENV/pd6mwLohrIP66SJOApiZCzT9/KZex2EicG05 q20zXRumx/Mi+dqvWjubV+r6m9+SJ4r4Q7xyvCQiwWOGvwFPrUxEeD/B4YbXD41ha2yymC dTJbzjTvRJ9N47OfOMgpC8B6GoNpA4BJUFdojsZq2jL/X3PPIAFJ4/EkIT0qD/swzgVSfd GIhP2ucVoRc4kvbfxuO3NG9bSj3rdF1hdam4jXrmoerw+yE7hJSy2VeFGj52Mw== ARC-Authentication-Results: i=2; aspmx1.migadu.com; dkim=pass header.d=blackmesatech.com header.s=dreamhost header.b=bBbwWH5v; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=none; arc=pass ("mailchannels.net:s=arc-2022:i=1") ARC-Seal: i=2; s=key1; d=yhetil.org; t=1716299984; a=rsa-sha256; cv=pass; b=K59Yyj4duKDa9DuzrdroY66OTnGvMu9MOM49xtH9dxnqEJxiVZGPdYPTwis9Ksl5rv48qe uICwzYEhNVVUrQbA6yPxU2IGwLK8WR+/N99nxI7d3vrwzuSlGJvE4pXbai8mxlvweE6S9H RsL10AUC7m0qlIYDIyk4oRUgYXZaJKukdhH+9xSmawP+tU59yKeQcHmcD4eBYeM6NJftv8 9dN8yWqr1B3cMP65ote6dvBH3sBX51eeA1E7nvcASZCPjnTPSSD7ABURUV7PkPoZjZk2w8 qJwPuqW5sdILXEtAqvpKBVGZ9XGkHx3clz9lROTpvN+iT4oWeLMyV0CTvVEzPA== 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 158C13E431 for ; Tue, 21 May 2024 15:59:44 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s9Q14-0008BT-4J; Tue, 21 May 2024 09:58:58 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s9Q10-0008AO-Ee for emacs-orgmode@gnu.org; Tue, 21 May 2024 09:58:54 -0400 Received: from slategray.cherry.relay.mailchannels.net ([23.83.223.169]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s9Q0y-00036Z-HT for emacs-orgmode@gnu.org; Tue, 21 May 2024 09:58:54 -0400 X-Sender-Id: dreamhost|x-authsender|cmsmcq@blackmesatech.com Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id EFBE2542A2C; Tue, 21 May 2024 13:58:50 +0000 (UTC) Received: from pdx1-sub0-mail-a208.dreamhost.com (unknown [127.0.0.6]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 991CD541D51; Tue, 21 May 2024 13:58:50 +0000 (UTC) ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1716299930; a=rsa-sha256; cv=none; b=WhVhFUNK+KcgvB05AKh8lD0YeW0u8bHZ5w94dG11xH2RVLSmKgFHYYmo9wQdaFB4fQVsXL VRht2mD/5o4iU1RgIgHmuHIfBbQMihoceSj6j7E6JQJIT20QSEbFJ4zWrxR8TWQpHg5hFE +XH9wQh+Q2CvsuDG1FfShoQIPLZiGfOMsH6LqhdHqX34UgvCssGyLH47Et8hLl+9YnB8qf im8pKD+BAw8QC3kpLeLY/4U71+ehAfONXrg0s7aiIA6vqyZPTYC8tOPhAqF75F8qWoqq6D YpDnasjj9mgQUCxS2CAdFt1HzOwiEztnOLyMO/Jw0Lm1xN91yHwPBRNFYXvDTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1716299930; h=from:from: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:references:references:dkim-signature; bh=8jpSZo1H8yP59JLt2j+2Dxnapwx0peUT3LmSYclFMxg=; b=tlwRBmb0KMM/F7qe34VsV8KnboqIec0fXt+Zg7Q1wcjkbJykDkEfgE2kB6cKEyx2Bop6h+ TcKhcEHL80qOYdcwPJZkpnQOhvnX6PeAgNLp52rIHggJ7+vk1l32WygSbrZvXEEsw8XMCp 6I+/LBsrNZ8BFdrLPmuHEeTzL/atJorbueLA/+LdlG9TOgFjvYf2jMCEOhQtQIC0rwYT4f Cky/F1Ex4iXTJqD7gNq+ypF/yidRGew4xCBnQD0qefYQ61rzxZqaqVA972kt7PuQC5t3x5 yOHi4OokmOBQdIaG132K/UfHXi5YvIh6qSG3V4F+/RtyDgl+yRuVE7xMEX0iqQ== ARC-Authentication-Results: i=1; rspamd-68bbddc7f5-98lkc; auth=pass smtp.auth=dreamhost smtp.mailfrom=cmsmcq@blackmesatech.com X-Sender-Id: dreamhost|x-authsender|cmsmcq@blackmesatech.com X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|cmsmcq@blackmesatech.com X-MailChannels-Auth-Id: dreamhost X-Eight-Average: 7a16ff487abd1188_1716299930853_2372254917 X-MC-Loop-Signature: 1716299930853:1995816823 X-MC-Ingress-Time: 1716299930853 Received: from pdx1-sub0-mail-a208.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.107.48.240 (trex/6.9.2); Tue, 21 May 2024 13:58:50 +0000 Received: from gemma.adelantecaucus.org (h79.217.186.173.dynamic.ip.windstream.net [173.186.217.79]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: cmsmcq@blackmesatech.com) by pdx1-sub0-mail-a208.dreamhost.com (Postfix) with ESMTPSA id 4VkGHt0gmxzCc; Tue, 21 May 2024 06:58:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=blackmesatech.com; s=dreamhost; t=1716299930; bh=8jpSZo1H8yP59JLt2j+2Dxnapwx0peUT3LmSYclFMxg=; h=From:To:Cc:Subject:Date:Content-Type; b=bBbwWH5vWpxn6LhjSkFi3wC4KcWZKc9PhGCo23oAXPOk02m+M7B5OCdVY5frOQ3St bCOI10skO0hAENHLX+Fy7YhK2ydGMh0TVIq1bDH2IhmAxgHGQfsGqBle83uj0G2Okn J0eH0AO08hndTx3cfB0SaHajV2o37sNZSDe3eJxhHmOstSj/OlOQt0MqBH0hcZqN70 LU2gFrkkI2ZDmqkMZBYmhR/3YBSNd23dbVGwsE26M0atKBYwzv069TOyGJ2I+bm7IK TF+faiVUYoLec11bg+QhtngSK9YD3lfTbePNzJtsbdGxXDBbUBtreHEBRHcLFf3OZI HP6/EcowQHBKw== References: <87jzjov2ll.fsf@blackmesatech.com> <87seybicy5.fsf@localhost> User-agent: mu4e 1.6.10; emacs 28.2 From: "C. M. Sperberg-McQueen" To: Ihor Radchenko Cc: emacs-orgmode@gnu.org Subject: Re: [BUG] Reference chains (C refers to B refers to A) in tangle do not behave as expected [9.5.5 (release_9.5.5 @ /usr/local/share/emacs/28.2/lisp/org/)] Date: Tue, 21 May 2024 07:55:28 -0600 In-reply-to: <87seybicy5.fsf@localhost> Message-ID: <87ed9vtgfb.fsf@blackmesatech.com> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=23.83.223.169; envelope-from=cmsmcq@blackmesatech.com; helo=slategray.cherry.relay.mailchannels.net 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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.29 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-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -8.06 X-Spam-Score: -8.06 X-Migadu-Queue-Id: 158C13E431 X-Migadu-Scanner: mx13.migadu.com X-TUID: 0qhwoYVCel/B Thank you for the response. I am sorry to say I do not understand it. You say that non-expansion of references in the code block Baker is expected "when it does not have :noweb tangle". > ... When retrieving the code for Baker block, Org mode goes to that > block and cleans up its text according to that block's > expansion. However, for Baker block, when it does not have :noweb > tangle, the <<...>> in the code are treated literally. The problem I am reporting is that the <<...>> in the code of Baker are treated literally even when Baker DOES have :noweb tangle. Thanks. Michael Sperberg-McQueen Ihor Radchenko writes: > "C. M. Sperberg-McQueen" writes: > >> Consider the following literate program in org mode: >> >> ................ make-abc.org: >> #+title: Minimal example >> #+date: 20 May 2024 >> >> The first letter is A. >> #+name: Able >> #+begin_src txt >> A is for application. >> #+end_src >> >> The second letter is B. It follows A. >> #+name: Baker >> #+begin_src txt :noweb tangle >> <> >> B is for beta-tester. >> #+end_src >> >> The third letter is C. We'll stop here. >> #+name: Charlie >> #+begin_src txt :tangle abc.txt :noweb tangle >> <> >> C is for coder. >> #+end_src >> >> Bottom line: two-level inclusions work only if the middle layer (here, >> /Baker/) has ~:noweb yes~. Using ~:noweb tangle~ on /Baker/ produces >> the same results as using ~:noweb no~. > > Yes, and it is expected. > >> ... >> In the org-mode manual [1], the meaning of :noweb tangle is described >> as: "Expansion of noweb syntax references in the body of the code block >> when tangling. No expansion when evaluating or exporting." I think that >> running org-babel-tangle counts as tangling, so I expect the noweb >> syntax references inside of code block Baker to be expanded. > > They are indeed expanded - there is a single noweb reference in Charlie > block - <>. It is expanded to the code contained in the Baker > block. When retrieving the code for Baker block, Org mode goes to that > block and cleans up its text according to that block's > expansion. However, for Baker block, when it does not have :noweb > tangle, the <<...>> in the code are treated literally. > > In other words, each noweb reference is expanded in its own context, > according to each block's own header arguments. > > Not a bug. > Canceled. -- C. M. Sperberg-McQueen Black Mesa Technologies LLC http://blackmesatech.com