From: Neil Jerram <neiljerram@gmail.com>
To: ian martins <ianxm@jhu.edu>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: consistent behavior across babel languages
Date: Thu, 26 Nov 2020 14:42:42 +0000 [thread overview]
Message-ID: <CAKuG=vtFeeODc1qcbVXfgMnr6nRMRpuuFfXjveXcAP1yTaS7=A@mail.gmail.com> (raw)
In-Reply-To: <CAC=rjb5xe7z7Ed=rKbWL4rEZj3oqdquvTVZZhmRgfe5maVJezA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
On Wed, 25 Nov 2020 at 05:20, ian martins <ianxm@jhu.edu> wrote:
> Something I've found challenging is the inconsistency between babel
> languages. It makes it difficult for a babel user to get a source
> block to do what they want, or for a babel developer to even know what
> correct behavior is.
>
> I'm not sure if anything can be done since changes will likely break
> existing behavior, but it's good to at least know what the rule is and
> where the exceptions to the rule are. To that end I started a page on
> worg [1] to document current behavior for actions taken across babel
> languages.
>
> [1] https://orgmode.org/worg/org-contrib/babel/languages/lang-compat.html
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.
[-- Attachment #2: Type: text/html, Size: 1665 bytes --]
next prev parent reply other threads:[~2020-11-26 14:43 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 [this message]
2020-11-27 13:47 ` ian martins
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='CAKuG=vtFeeODc1qcbVXfgMnr6nRMRpuuFfXjveXcAP1yTaS7=A@mail.gmail.com' \
--to=neiljerram@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ianxm@jhu.edu \
/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).