From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neeum Zawan Subject: Re: Regression bug in tangle/weave Date: Sat, 09 Jul 2011 09:14:56 -0700 Message-ID: <877h7rtoqn.fsf@fester.com> References: <1309447445.43453.YahooMailNeo@web81602.mail.mud.yahoo.com> <8762nn8945.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([140.186.70.92]:49001) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QfaBn-000844-IL for emacs-orgmode@gnu.org; Sat, 09 Jul 2011 12:15:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QfaBl-0001XE-So for emacs-orgmode@gnu.org; Sat, 09 Jul 2011 12:15:31 -0400 Received: from lo.gmane.org ([80.91.229.12]:52910) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QfaBl-0001X1-FP for emacs-orgmode@gnu.org; Sat, 09 Jul 2011 12:15:29 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QfaBk-0007yV-5W for emacs-orgmode@gnu.org; Sat, 09 Jul 2011 18:15:28 +0200 Received: from c-71-237-233-41.hsd1.or.comcast.net ([71.237.233.41]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 Jul 2011 18:15:28 +0200 Received: from mailinglists by c-71-237-233-41.hsd1.or.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 Jul 2011 18:15:28 +0200 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 Eric Schulte writes: > Hi, > > Indeed this example below no longer works, however I believe the new > behavior is both desired and permanent. I'll explain and include an > option for how your example could be restructured to work with the new > code. > > We ran into problems automatically removing trailing newlines from code > block bodies as in some languages (looking at you Python and Haskell) > things like trailing newlines are of syntactic importance. In your > example this behavior results in the insertion of newlines after > file-name and file-version. Babel is careful to preserve line prefixes > when expanding references in comments, so it then reproduces the > > # Generated from > > portion of that line for every line of the expanded noweb references. > > I would suggest the following alternatives, either using a data > references in stead of a code block reference as in the file-version > example below, or using an evaluated code block as in the file-name > example below. Hope this helps. Oh dear. Am I to blame for this? When I reported the newline issue, somewhere in the back of my mind I knew it probably would have some ugly consequences. Now I see them. An evaluated code block seems inelegant/confusing if one intends to export that code as part of the document. A data reference seems OK, but I take it you can't have references within it? Unfortunately, I see no easy solution...