From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rainer M Krug Subject: Re: [BABEL] BUG Re: Omitting try/catch blocks from tangled R code? Date: Thu, 20 Mar 2014 10:22:41 +0100 Message-ID: References: <52F498AE.6090802@krugs.de> <87siruamo3.fsf@gmail.com> <52F5326C.7010505@krugs.de> <877g7syio6.fsf@gmail.com> <87txawwwh6.fsf@gmail.com> <87r45xeabf.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35551) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQZBm-0001Co-7l for emacs-orgmode@gnu.org; Thu, 20 Mar 2014 05:23:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WQZBb-0004iC-Tj for emacs-orgmode@gnu.org; Thu, 20 Mar 2014 05:23:02 -0400 Received: from mail-we0-f175.google.com ([74.125.82.175]:41505) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQZBb-0004hu-LB for emacs-orgmode@gnu.org; Thu, 20 Mar 2014 05:22:51 -0400 Received: by mail-we0-f175.google.com with SMTP id q58so369278wes.34 for ; Thu, 20 Mar 2014 02:22:50 -0700 (PDT) In-Reply-To: <87r45xeabf.fsf@gmail.com> (Eric Schulte's message of "Wed, 19 Mar 2014 22:57:40 -0600") 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: Eric Schulte Cc: emacs-orgmode@gnu.org, Charles Berry --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Eric Schulte writes: > Charles Berry writes: > >> 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, a= nd >>> > are only there for the exported engine. So I would either revert to t= he >>> > 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. >>>=20 >>> 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. >> > > In addition to noweb, there are cases where variable expansion is useful > in tangled code. > > The simplest option is to move things like try/catch blocks out of the > code block expansion function, and into the execution function. Then if > other language present similar constructs (which we want to add to > execution by default but never want to tangle), we can think about > abstracting this out into some new level of code block expansion. > > Thoughts? Makes perfect sense to me, and would definitely be the better place to add them. If one wants enclosing code in the tangling, there is always the :epilogue and :prologue header arguments, and the try/catch should be considered as internal to the execution. Rainer > >> >> Best, >> >> Chuck >> >> =2D-=20 Rainer M. Krug email: Rainerkrugsde PGP: 0x0F52F982 --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBAgAGBQJTKrNmAAoJENvXNx4PUvmC5SoH/0/0JKQ9c4ZQCoBXQ2BmKQk7 ENqrkY29n4yUAddWxstrTKswU4SEZKkUuE5vhicC3mvG6w9ELzwHoXz7qMMh8Qwv mSZf/5LUaCGqMivxanI86XLtFziud6D08uq2Ph43OI8rgVNpiae8YJXH6hY8girl jH3jdVjvukOvf5+LiH2rLT80J6FHzjLCodZ3ksJXlBaJB+u3fO7/g4TZWq6QytE4 S+aDVBPL1/ixcSa/qxEozn3Zax6WtJxZRAjS43bWe/1cYlNRlSC5kX2L00+7E7PO p55b25uDd6EEyemG6+JcxNtc+96GHK9F2H0qK4E2o7eGRQMPnq/wW23om8xAh/A= =/wl/ -----END PGP SIGNATURE----- --=-=-=--