From mboxrd@z Thu Jan 1 00:00:00 1970 From: Charles Berry Subject: Re: [BABEL] BUG Re: Omitting try/catch blocks from tangled R code? Date: Wed, 19 Mar 2014 19:07:02 +0000 (UTC) Message-ID: References: <52F498AE.6090802@krugs.de> <87siruamo3.fsf@gmail.com> <52F5326C.7010505@krugs.de> <877g7syio6.fsf@gmail.com> <87txawwwh6.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41254) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQLq0-0000WI-3j for emacs-orgmode@gnu.org; Wed, 19 Mar 2014 15:07:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WQLps-0007nr-Qq for emacs-orgmode@gnu.org; Wed, 19 Mar 2014 15:07:40 -0400 Received: from plane.gmane.org ([80.91.229.3]:36886) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQLps-0007nZ-Jm for emacs-orgmode@gnu.org; Wed, 19 Mar 2014 15:07:32 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WQLpp-0001Yh-4V for emacs-orgmode@gnu.org; Wed, 19 Mar 2014 20:07:29 +0100 Received: from 137.110.32.33 ([137.110.32.33]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Mar 2014 20:07:29 +0100 Received: from ccberry by 137.110.32.33 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Mar 2014 20:07:29 +0100 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 John Hendy gmail.com> writes: [deleted] > > > > I think the default behavior should be reverted, as tangling and > > exporting are two different things. When I tangle, I want to see the > > code blocks as they are in the org document (with possible variables and > > expansions) but not to create files where I do not put it explicitly > > into a code block. These wrappers have nothing to do with the code, and > > are only there for the exported engine. So I would either revert to the > > original behavior, or, introduce a new header argument, > > e.g. :include-wrappers, which would, if set to t, include the export > > wrappers in the tangled file. This might be useful for debugging > > exporting of code block results, but not for general tangling. > > Thanks for chiming in. This was my gut reaction to the default > behavior. I guess we're still only a sample size of 2, but > intuitively, I would think that tangling would be a separate beast in > most cases from exporting. Just to have it on the record, if I tangle, > it's usually to take the code I've used in something like a Beamer > presentation or document and combine it into a single .R file so > someone can run it without needing Org-mode. ]deleted] Sorry to be late to add my $0.02... I never want the try/catch wrappers. But noweb is indispensable. I use noweb a lot to organize and collect blocks. In some cases, I export them and in others I just tangle them. I hope that the revised code will allow me to turn off try/catch wrapping and still be able to use noweb when tangling or exporting. Best, Chuck