From: Ihor Radchenko <yantar92@posteo.net>
To: "Thomas S. Dye" <tsd@tsdye.online>
Cc: emacs-orgmode@gnu.org
Subject: Re: [TASK] Move babel backend docs from WORG to Org manual
Date: Fri, 13 Dec 2024 18:54:07 +0000 [thread overview]
Message-ID: <87cyhvh0s0.fsf@localhost> (raw)
In-Reply-To: <87pllzuv0o.fsf@tsdye.online>
"Thomas S. Dye" <tsd@tsdye.online> writes:
> I'm happy to volunteer and will start by creating
> ob-doc-<lang>.org files for undocumented and unmaintained
> languages: comint, F90, forth, sed, ocaml, ruby, and sass.
Note that ob-comint is not a language, but a helper library used to
implement session support.
> ... I
> don't know or use any of these languages. If someone else does
> know one and would like to jump in, LMK.
Any specific reason why you chose the languages you don't know? May it
be easier to start from parts you are more familiar with?
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-12-13 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 19:52 [TASK] Move babel backend docs from WORG to Org manual Ihor Radchenko
2024-12-10 20:45 ` Thomas S. Dye
2024-12-13 18:50 ` Ihor Radchenko
2024-12-13 18:54 ` Ihor Radchenko [this message]
2024-12-13 21:39 ` Thomas S. Dye
2024-12-14 6:58 ` [TASK] Documenting ob-fortran, ob-forth, ob-sed, ob-ocaml, ob-ruby, and ob-sass (was: [TASK] Move babel backend docs from WORG to Org manual) Ihor Radchenko
2024-12-10 23:45 ` [TASK] Move babel backend docs from WORG to Org manual Suhail Singh
2024-12-13 19:05 ` Ihor Radchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cyhvh0s0.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.online \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.