Content-Length: 7839 | pFad | https://list.orgmode.org/87seqqg38b.fsf@localhost

emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Ihor Radchenko <yantar92@posteo.net>
To: "Thomas S. Dye" <tsd@tsdye.online>
Cc: emacs-orgmode@gnu.org
Subject: [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)
Date: Sat, 14 Dec 2024 06:58:44 +0000	[thread overview]
Message-ID: <87seqqg38b.fsf@localhost> (raw)
In-Reply-To: <87ikrnuust.fsf@tsdye.online>

"Thomas S. Dye" <tsd@tsdye.online> writes:

>> 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?
>
> These lack documentation on Worg, that's all.

Got it.
Let me then change the subject here to indicate that these languages are
being worked on.

-- 
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-14  6:58 UTC|newest]

Thread overview: 11+ 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
2024-12-13 21:39     ` Thomas S. Dye
2024-12-14  6:58       ` Ihor Radchenko [this message]
2025-01-21 19:46         ` [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
2025-01-21 20:11           ` [TASK] Documenting ob-fortran, ob-forth, ob-sed, ob-ocaml, ob-ruby, and ob-sass Thomas S. Dye
2025-01-21 20:16             ` 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

  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=87seqqg38b.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

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).