From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Jarmo Hurri <jarmo.hurri@iki.fi>, emacs-orgmode@gnu.org
Subject: Re: Babel CALL no longer produces HTML output
Date: Mon, 25 Jul 2016 08:55:39 -0700 [thread overview]
Message-ID: <alpine.OSX.2.20.1607250845400.540@charles-berrys-macbook.local> (raw)
In-Reply-To: <87shuyw3hg.fsf@saiph.selenimh>
On Mon, 25 Jul 2016, Nicolas Goaziou wrote:
> Hello,
>
> "Thomas S. Dye" <tsd@tsdye.com> writes:
>
>> Nicolas Goaziou writes:
>>
>>> You may want to add (:eval . "yes") to
>>> `org-babel-default-lob-header-args' if you disagree.
>>
>> Perhaps this should be added to the default value of
>> org-babel-default-lob-header-args for the sake of legacy code?
>
> I don't think so, for three reasons:
>
> 1. `org-babel-default-lob-header-args' didn't include this association previously;
>
> 2. unlike to :exports, there is no obvious default value for the :eval
> argument; the expected default value would be to unset :eval, which
> requires another mechanism;
>
> 3. I think it is dangerous to assume and Babel call can be evaled, even if
> the original source block cannot; after all, the user explicitly
> marked the original code block with ":eval no" for a reason.
>
Fair enough.
I can think of reasons why a user would want to do this, but the current
setup accomodates those pretty well.
Chuck
next prev parent reply other threads:[~2016-07-25 15:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 12:14 Babel CALL no longer produces HTML output Jarmo Hurri
2016-07-23 12:48 ` Christian Moe
2016-07-23 13:03 ` Jarmo Hurri
2016-07-24 17:00 ` Christian Moe
2016-07-23 16:10 ` Charles C. Berry
2016-07-23 16:51 ` Nicolas Goaziou
2016-07-23 22:16 ` Charles C. Berry
2016-07-25 7:08 ` Nicolas Goaziou
2016-07-25 7:48 ` Thomas S. Dye
2016-07-25 8:01 ` Nicolas Goaziou
2016-07-25 15:55 ` Charles C. Berry [this message]
2016-07-25 17:27 ` Thomas S. Dye
2016-07-23 16:52 ` Jarmo Hurri
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=alpine.OSX.2.20.1607250845400.540@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=jarmo.hurri@iki.fi \
--cc=mail@nicolasgoaziou.fr \
/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).