From: ian martins <ianxm@jhu.edu>
To: Neil Jerram <neiljerram@gmail.com>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: consistent behavior across babel languages
Date: Fri, 27 Nov 2020 08:47:53 -0500 [thread overview]
Message-ID: <CAC=rjb7r_kbJ2qSL9jN1X1=3Ln=y-MyFUE=voxstrQxf-JHfdg@mail.gmail.com> (raw)
In-Reply-To: <CAKuG=vtFeeODc1qcbVXfgMnr6nRMRpuuFfXjveXcAP1yTaS7=A@mail.gmail.com>
On Thu, Nov 26, 2020 at 9:42 AM Neil Jerram <neiljerram@gmail.com> wrote:
> Wonderful, thank you. I have been thinking it would be nice to have a test suite along these lines, but detailed doc like this is more feasible and maintainable.
A test suite is a good idea as a next step to protect correct
behaviors. I want to first look at actual behaviors and get agreement
on correct behaviors first. On the other hand, each of the language's
test suites should cover the same ground so a separate test suite may
not make sense.
> When time permits I will work on adding Scheme to this page.
Great, thanks!
> FWIW, I did not understand the "functional" and "scripting" terms that you use on this page.
>
> I've understood now, from https://orgmode.org/worg/org-contrib/babel/intro.html, that you mean "results: value" and "results: output". For me it would be better if you said that instead of "functional" and "scripting", as the former is what I can actually type in my Org files.
yes, it's in the manual as well [1], but I agree that alternating
between two sets of terms here is unnecessarily confusing. Will
change.
[1] https://orgmode.org/manual/Results-of-Evaluation.html#Results-of-Evaluation
prev parent reply other threads:[~2020-11-27 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 5:18 consistent behavior across babel languages ian martins
2020-11-25 7:05 ` Tim Cross
2020-11-25 19:36 ` Tom Gillespie
2020-11-26 3:45 ` ian martins
2020-11-26 10:20 ` Neil Jerram
2020-11-26 14:42 ` Neil Jerram
2020-11-27 13:47 ` 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=rjb7r_kbJ2qSL9jN1X1=3Ln=y-MyFUE=voxstrQxf-JHfdg@mail.gmail.com' \
--to=ianxm@jhu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=neiljerram@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).