From: "Thomas S. Dye" <tsd@tsdye.online>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ob-shell-test, test-ob-shell and introduction
Date: Mon, 22 Nov 2021 09:08:33 -1000 [thread overview]
Message-ID: <87y25g2eku.fsf@tsdye.online> (raw)
In-Reply-To: <17d48f09729.ddbece82213631.8340272801066201269@excalamus.com>
Aloha Matt,
Matt <matt@excalamus.com> writes:
> Hi,
>
> I'm interested in getting async into ob-shell.el. Since I've
> never contributed before, I figure it'd be good to start with a
> few easy tasks.
>
> It looks to me like the stdin and cmdline header args aren't
> documented anywhere (at least I couldn't find anything). To make
> sure I'm using them correctly before making a patch for the
> manual, here are some tests.
>
> Please let me know if things look okay. It wasn't clear to me
> how to send along a message with git send-email, so I formatted
> these patches and included them as an attachment. Is that fine?
>
> Thanks,
> Matt
Unfortunately, there is no ob-doc-shell.org at
worg/org-contrib/babel/languages/.
There is an ob-doc-template.org in case you'd like to contribute
ob-doc-shell.org :)
All the best,
Tom
--
Thomas S. Dye
https://tsdye.online/tsdye
next prev parent reply other threads:[~2021-11-22 19:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 18:37 [PATCH] ob-shell-test, test-ob-shell and introduction Matt
2021-11-22 18:43 ` Timothy
2021-11-24 18:48 ` Matt
2021-12-02 9:39 ` Timothy
2021-12-06 3:50 ` Matt
2021-12-06 4:50 ` Thomas S. Dye
2021-12-18 7:03 ` Matt
2021-12-18 20:51 ` Thomas S. Dye
2021-12-31 17:04 ` Thomas S. Dye
2021-12-31 19:18 ` Matt
2021-12-31 22:11 ` Thomas S. Dye
2022-01-02 4:32 ` Matt
2022-01-02 18:57 ` Thomas S. Dye
2022-01-05 17:12 ` Max Nikulin
2022-01-06 3:47 ` Matt
2022-01-07 16:18 ` Max Nikulin
2021-11-22 19:08 ` Thomas S. Dye [this message]
2021-11-23 4:42 ` [PATCH] ob-doc-shell.org (was [PATCH] ob-shell-test, test-ob-shell and introduction) Matt
2021-11-23 4:59 ` Thomas S. Dye
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=87y25g2eku.fsf@tsdye.online \
--to=tsd@tsdye.online \
--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).