From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Alan Dorman Subject: Tangle won't strip coderef labels? Date: Mon, 07 Jan 2013 11:47:09 -0500 Message-ID: <87mwwlx7n6.fsf@ironicdesign.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:60360) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsFqy-0000Iy-Ul for emacs-orgmode@gnu.org; Mon, 07 Jan 2013 11:47:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TsFqx-0000nT-TG for emacs-orgmode@gnu.org; Mon, 07 Jan 2013 11:47:12 -0500 Received: from nerissa.ironicdesign.com ([206.166.194.226]:48708) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsFqx-0000nF-OX for emacs-orgmode@gnu.org; Mon, 07 Jan 2013 11:47:11 -0500 Received: from localhost (localhost [127.0.0.1]) by nerissa.ironicdesign.com (Postfix) with QMQP id 8FD732B40375 for ; Mon, 7 Jan 2013 10:47:10 -0600 (CST) Received: from ogg.local (user-0c2h36k.cable.mindspring.com [24.40.140.212]) (Authenticated sender: mdorman@ironicdesign.com) by incoming.antespam.com (Postfix) with ESMTPSA id C87F12B40366 for ; Mon, 7 Jan 2013 10:47:09 -0600 (CST) 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org I've recently started to use Org-mode to write some small utilities in a literate style. I then stumbled upon the docs about coderef labels, which seemed like a great way to minimize having to basically repeat the content of code in the documentation about the utility's design. The only problem is that they aren't stripped during tangling. So if you have a doc like: #+BEGIN_SRC sh -n -r :noweb tangle :shebang #!/bin/sh :tangle test.sh echo "Working" (ref:working) #+END_SRC When you tangle the doc, you'll end up with: #!/bin/sh echo "Working" (ref:working) I'm assuming this isn't intended behavior, since I can't find anything in the docs about it. I appreciate any help---I've done some spelunking around the source, but it's not at all obvious to me how this all fits together, so I'm afraid I'm not able to offer a patch, assuming it's a bug. Mike.