From: Rainer M Krug <Rainer@krugs.de>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org, Charles Berry <ccberry@ucsd.edu>
Subject: Re: [BABEL] BUG Re: Omitting try/catch blocks from tangled R code?
Date: Thu, 20 Mar 2014 10:22:41 +0100 [thread overview]
Message-ID: <m2fvmd9qce.fsf@krugs.de> (raw)
In-Reply-To: <87r45xeabf.fsf@gmail.com> (Eric Schulte's message of "Wed, 19 Mar 2014 22:57:40 -0600")
[-- Attachment #1: Type: text/plain, Size: 2676 bytes --]
Eric Schulte <schulte.eric@gmail.com> writes:
> Charles Berry <ccberry@ucsd.edu> writes:
>
>> John Hendy <jw.hendy <at> 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.
>>
>
> 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
>>
>>
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2014-03-20 9:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 6:18 Omitting try/catch blocks from tangled R code? John Hendy
2014-02-07 8:26 ` [BABEL] BUG " Rainer M Krug
2014-02-07 16:47 ` Eric Schulte
2014-02-07 19:22 ` Rainer M Krug
2014-03-12 1:13 ` John Hendy
2014-03-17 15:00 ` Eric Schulte
2014-03-17 17:11 ` John Hendy
2014-03-17 17:44 ` Eric Schulte
2014-03-18 8:44 ` Rainer M Krug
2014-03-18 21:56 ` John Hendy
2014-03-19 19:07 ` Charles Berry
2014-03-20 4:57 ` Eric Schulte
2014-03-20 9:22 ` Rainer M Krug [this message]
2014-03-24 2:03 ` Eric Schulte
2014-03-24 10:22 ` Rainer M Krug
2014-03-24 13:16 ` Eric Schulte
2014-03-25 9:37 ` Rainer M Krug
2014-03-26 20:17 ` Eric Schulte
2014-03-28 8:32 ` Rainer M Krug
2014-03-28 8:51 ` Rainer M Krug
2014-03-30 14:19 ` Eric Schulte
2014-03-31 7:52 ` Rainer M Krug
2014-04-02 23:09 ` Eric Schulte
2014-04-07 7:59 ` Rainer M Krug
2014-04-11 2:35 ` Eric Schulte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2fvmd9qce.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).