Aloha Ihor,
Ihor Radchenko 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
Suhail Singh writes:
> Ihor Radchenko writes:
>
>> The general idea is to port files from
>> https://git.sr.ht/~bzg/worg/tree/master/item/org-contrib/babel into
>> Org manual.
>
> Do contributions to the Orgmode manual require copyright assignment to
> the FSF?
Yes.
For languages that are not b
"Thomas S. Dye" writes:
> I'm happy to volunteer and will start by creating
> ob-doc-.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
"Thomas S. Dye" writes:
> So, the first order of business is to ensure that all
> ob-doc-.org files on Worg are complete by i) creating
> missing files, ii) editing incomplete files, and iii) checking
> complete files?
>
> Then, once Worg holds complete documentation for each built-in
> langu
Ihor Radchenko writes:
> The general idea is to port files from
> https://git.sr.ht/~bzg/worg/tree/master/item/org-contrib/babel into
> Org manual.
Do contributions to the Orgmode manual require copyright assignment to
the FSF?
--
Suhail
Ihor Radchenko writes:
Dear all,
In my talk https://emacsconf.org/2024/talks/org-update, one of
the tasks
I announced was moving babel documentation from WORG to Org
manual.
Here, I would like to details what should be done for that task.
This is a big task, but we can split it into much s
