emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: Jarmo Hurri <jarmo.hurri@iki.fi>, emacs-orgmode@gnu.org
Subject: Re: Babel CALL no longer produces HTML output
Date: Sat, 23 Jul 2016 18:51:46 +0200	[thread overview]
Message-ID: <87fur0fgbh.fsf@saiph.selenimh> (raw)
In-Reply-To: <alpine.OSX.2.20.1607230853560.649@charles-berrys-macbook.local> (Charles C. Berry's message of "Sat, 23 Jul 2016 09:10:22 -0700")

Hello,

"Charles C. Berry" <ccberry@ucsd.edu> writes:

> IIUC, one result is that header args in the src block being called take 
> precedence over default header args. More below.

[...]

> I am not sure I find this new behavior to be an improvement.

Having default header args to take precedence over local ones seems
counter-intuitive. It makes it harder to override them, and harder to
reason about the current active headers.

OTOH, inheriting :exports property may not be optimal. In particular,
":exports code" for a Babel call is probably nonsensical. Perhaps
a solution would be to keep the current behaviour and make an exception
for :exports, which would always be `results' for Babel calls.

WDYT?

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2016-07-23 16:51 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 [this message]
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
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=87fur0fgbh.fsf@saiph.selenimh \
    --to=mail@nicolasgoaziou.fr \
    --cc=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=jarmo.hurri@iki.fi \
    /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).