From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Miele Subject: Re: noweb multiple block together Date: Mon, 25 Nov 2019 06:24:57 +0000 Message-ID: <87y2w4bhhi.fsf@gmail.com> References: <878so4por9.fsf@gmail.com> Reply-To: sebastian.miele@gmail.com Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:38430) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZ7o1-0001do-EJ for emacs-orgmode@gnu.org; Mon, 25 Nov 2019 01:25:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iZ7nz-0005X9-ES for emacs-orgmode@gnu.org; Mon, 25 Nov 2019 01:25:05 -0500 Received: from mail-wr1-x42b.google.com ([2a00:1450:4864:20::42b]:37441) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iZ7ny-0005Ui-3P for emacs-orgmode@gnu.org; Mon, 25 Nov 2019 01:25:03 -0500 Received: by mail-wr1-x42b.google.com with SMTP id t1so16361945wrv.4 for ; Sun, 24 Nov 2019 22:25:01 -0800 (PST) Received: from tisch ([2a02:908:175c:4260:5ffc:7882:6024:ca5b]) by smtp.gmail.com with ESMTPSA id v128sm7842177wmb.14.2019.11.24.22.24.58 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 24 Nov 2019 22:24:59 -0800 (PST) In-reply-to: <878so4por9.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Hi Ken, Ken Mankoff writes: > When tangling blocks, I can tangle multiple blocks by setting a > (sub)-tree level property, or ":tangle foo" in multiple headers. Is > there a way to achieve the same thing with noweb? > > I've tried giving multiple blocks the same "+name:" and then <>, > but only one seems to be included. Does this feature exist through > some mechanism? A block named by #+name: should always be unique per file. Otherwise the Org tangling code that I looked at until now (which is most or even all in the master branch) just uses the first one found, without checking for duplicates. On the other hand there is the possibility to give a common name to multiple blocks via the header arg :noweb-ref. That works in the way you looking for. There is a further difference between these two kinds of naming: With blocks named by :noweb-ref it is not possible to do something like <>. Only <>, i.e. plain inclusion, is possible. Best wishes Sebastian