From: ian martins <ianxm@jhu.edu>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: Tim Cross <theophilusx@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: consistent behavior across babel languages
Date: Wed, 25 Nov 2020 22:45:15 -0500 [thread overview]
Message-ID: <CAC=rjb75-geWFpGUOi4OrusWkF+UH8pXm2swnyKiaU8v_5LrAg@mail.gmail.com> (raw)
In-Reply-To: <CA+G3_PMF6uRQCABso=3QVU-b6E5UMsBMTYk0PgFdsqgdWjOrFQ@mail.gmail.com>
On Wed, Nov 25, 2020 at 2:06 AM Tim Cross <theophilusx@gmail.com> wrote:
>
> 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.
That would be great.
On Wed, Nov 25, 2020 at 2:39 PM Tom Gillespie <tgbugs@gmail.com> wrote:
>
> 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?
Yes, definitely. My plan is to add sections for major features or
feature groups and have a table for each section, and when that stops
working to think of something else. I am planning a section for
variables focusing on passing lists and tables which will probably
look a lot like the section on returning list and tables. There should
definitely be a section on TRAMP.
next prev parent reply other threads:[~2020-11-26 3:46 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 [this message]
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='CAC=rjb75-geWFpGUOi4OrusWkF+UH8pXm2swnyKiaU8v_5LrAg@mail.gmail.com' \
--to=ianxm@jhu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=tgbugs@gmail.com \
--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).