emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tom Gillespie <tgbugs@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: consistent behavior across babel languages
Date: Wed, 25 Nov 2020 14:36:48 -0500	[thread overview]
Message-ID: <CA+G3_PMF6uRQCABso=3QVU-b6E5UMsBMTYk0PgFdsqgdWjOrFQ@mail.gmail.com> (raw)
In-Reply-To: <87sg8x7w6i.fsf@gmail.com>

Hi Ian,
    Thanks for getting this started. I have been collecting a list of
org babel issues and worg is definitely a better place to put them
than in one big email. Since there are so many different features that
a babel language implementation can support I don't want to try to put
them all in one table quite yet but I think it may be helpful to do so
eventually. Until that time does it make sense to add new sections to
the file that cover specific features? For example I have tests on
TRAMP support and/or support for execution via a remote session that I
would like to add from my internal notes. Can I add it as a new
section? Best!
Tom



On Wed, Nov 25, 2020 at 2:06 AM Tim Cross <theophilusx@gmail.com> wrote:
>
>
> ian martins <ianxm@jhu.edu> writes:
>
> > 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
>
>
> this is a great initiative Ian. First step in addressing inconsistencies
> is documenting them. I will try to allocate time on the weekend to
> review what you have and see if there are any I know of which you have
> not included.
>
>
> --
> Tim Cross
>


  reply	other threads:[~2020-11-25 19:40 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 [this message]
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

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='CA+G3_PMF6uRQCABso=3QVU-b6E5UMsBMTYk0PgFdsqgdWjOrFQ@mail.gmail.com' \
    --to=tgbugs@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@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).