From: ian martins <ianxm@jhu.edu>
To: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: default :results
Date: Tue, 17 Nov 2020 07:40:06 -0500 [thread overview]
Message-ID: <CAC=rjb6P_6U9-Hzq7LBfL2s_MF3sztWFO6s1qNgKuaprpewPaA@mail.gmail.com> (raw)
In-Reply-To: <CAC=rjb4TvCV3G=Zg4uTXtPpDjJopJ8m1S-3ZRHAivr9Xzr6hWA@mail.gmail.com>
On Sat, Nov 14, 2020 at 5:27 AM ian martins <ianxm@jhu.edu> wrote:
>
> On Wed, Nov 11, 2020 at 3:04 AM Bastien <bzg@gnu.org> wrote:
> >
> > The default for ob-shell execution was to use the output, not the
> > value. Then we had a long discussion, leading to this:
> >
> > - The default (no :result) is to display the functional value
> >
> > - For some languages, it may break expectations, so in this case we
> > allow a variable that let the default (no :result) use the output
> > instead of the functional value.
> >
> > This is what is being done for ob-shell.el where we have
> > `org-babel-shell-results-defaults-to-output' set to `t'.
> >
> > See https://orgmode.org/list/877dt5trjr.fsf@bzg.fr/ for the conclusion
> > of the discussion.
>
> I agree with your reasoning. I already reverted the behavior, but
> Instead of adding a `org-babel-java-results-defaults-to-output
> variable' I set the default in `org-babel-default-header-args:java'.
> It was better because it didn't add a new variable, but worse because
> it isn't customizable. Should I change it?
shortly after sending this I reverted another change I'd made to
default behavior by setting it in
`org-babel-default-header-args:java'. Another benefit of doing it here
is that this variable becomes a list of ways in which a language
doesn't follow normal babel default conventions, making it easy to
find.
prev parent reply other threads:[~2020-11-17 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 2:01 default :results ian martins
2020-11-11 8:03 ` Bastien
2020-11-14 10:27 ` ian martins
2020-11-17 12:40 ` ian martins [this message]
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='CAC=rjb6P_6U9-Hzq7LBfL2s_MF3sztWFO6s1qNgKuaprpewPaA@mail.gmail.com' \
--to=ianxm@jhu.edu \
--cc=emacs-orgmode@gnu.org \
/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).