emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.online>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [TASK] Move babel backend docs from WORG to Org manual
Date: Fri, 13 Dec 2024 11:39:30 -1000	[thread overview]
Message-ID: <87ikrnuust.fsf@tsdye.online> (raw)
In-Reply-To: <87cyhvh0s0.fsf@localhost> (Ihor Radchenko's message of "Fri, 13 Dec 2024 18:54:07 +0000")

Aloha Ihor,

Ihor Radchenko <yantar92@posteo.net> 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.

I've been documenting the Babel languages on Worg for a few years 
with the hope that someday all the core languages would have their 
own ob-doc file.  Your talk at EmacsConf2024 inspired me to get 
back at it.

Note that there are some maintained languages that aren't 
documented, as well: groovy, calc, haskell, and processing.
-- 
Thomas S. Dye
https://tsdye.online/tsdye


  reply	other threads:[~2024-12-13 21:40 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
2024-12-13 21:39     ` Thomas S. Dye [this message]
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

  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=87ikrnuust.fsf@tsdye.online \
    --to=tsd@tsdye.online \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).