Re: Worg: issue with org-tools page

[Ihor Radchenko]

Bastien Guerry <bzg@gnu.org> writes:

>> So, there is still a problem with ESS installation.
>> We may need to update the build manifest yet more.
>> Probably "elpa-ess" is installed into some weird place, out of
>> load-path.
>
> I added the load-path for ess, this seems to work.

May it be enough to drop --quick in Emacs call from publish.sh instead
of manually adding system-installed Emacs packages?

--quick implies -q --no-site-file --no-splash and --no-site-file
prevents loading Emacs packages installed by apt, AFAIU.

So, we might simply use --no-init-file --no-splash.

Also, re: f32704bbbd97 publish.sh: Set ess vars to nil

We probably need to deal with it on Org side.
See 
https://list.orgmode.org/orgmode/alpine.DEB.2.22.394.2211132209230.150678@shell3.miskatonic.org/

> I also added the gnuplot dependency in the build manifest, hopefully
> this fixes the last error I've seen.

There seems to be a general problem with some blocks being executed when
they are not supposed to.

In 515c8b75 org-contrib/babel/examples/Rpackage.org, the problematic
block is not supposed to be evaluated during export!
Similar situation with the latest failure
https://builds.sr.ht/~bzg/job/1035804 where blocks in
data-collection-analysis.org are clearly not intended for evaluation.

May we just set #+PROPERTY: header-args :eval no-export across examples?
Or, more generally, avoid evaluating blocks unless explicitly enabled
across all Org files (to be future-proof).

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
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>