Ihor Radchenko <[email protected]> writes:
"Thomas S. Dye" <[email protected]> writes:
I see 11 languages added to org-babel-load-languages list in
publish.sh and numerous warnings in .build.yml for languages
not
on the list:
Warning (emacs): org-export: No org-babel-execute function
for
octave. Not updating exported results.
IIRC, many of the ob-doc-* files expect the Worg server to
generate and display a graphic file. Would it help if I
uploaded
graphic files and changed the ob-doc-* files to point to these
graphics, rather than expecting the server to generate them on
its
own?
This should probably be a question to Christian.
I thought about his in the past and noted the following:
1. Currently, we have to set up all the extra babel requirements
on CI build to make things work. Sometimes, it is a bit
tricky.
On the other hand, it serves as an additional layer for
detecting
ob-*.el test failures (although WORG is definitely not the
place to
test these things properly)
2. Some babel languages are already configured on CI, so things
are
partially working. Whether those need to be removed is a
question, if
we decide to generate images and code output manually
3. From time to time, we need to re-configure CI (with new
debian
releases). Maintaining babel configuration is a bit of extra
maintenance burden.
4. Adding images means a bit more work for people writing worg
pages.
Christian, I'm happy to edit the ob-doc-*.org files to
standardize. If the CI approach is better, then I'm happy with
that, too.
All the best,
Tom
--
Thomas S. Dye
https://tsdye.online/tsdye
