emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Bastien Guerry <bzg@gnu.org>
Cc: Karl Voit <news2042@Karl-Voit.at>, emacs-orgmode@gnu.org
Subject: Re: Worg: issue with org-tools page
Date: Sun, 06 Aug 2023 06:34:54 +0000	[thread overview]
Message-ID: <87350wk7ap.fsf@localhost> (raw)
In-Reply-To: <87a5v5weg1.fsf@bzg.fr>

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>


  reply	other threads:[~2023-08-06  6:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-09 15:37 Worg: issue with org-tools page Karl Voit
2023-04-09 16:53 ` Ihor Radchenko
2023-04-09 21:51   ` Karl Voit
2023-04-18 12:29     ` Ihor Radchenko
2023-04-18 13:48       ` Karl Voit
2023-07-29 12:14         ` Ihor Radchenko
2023-07-30  2:57           ` Max Nikulin
2023-07-30  6:40             ` Ihor Radchenko
2023-07-30  7:38               ` Max Nikulin
2023-07-30  9:16                 ` Ihor Radchenko
2023-07-31 16:12                   ` Max Nikulin
2023-07-31 16:41                     ` Ihor Radchenko
2023-08-05 12:14                       ` Max Nikulin
2023-08-05 12:23                         ` Ihor Radchenko
2023-08-06 11:31                           ` Max Nikulin
2023-08-06 15:08                             ` Ihor Radchenko
2023-08-09  7:44                               ` Ihor Radchenko
2023-08-09 10:35                                 ` Max Nikulin
2023-08-04 10:21           ` Bastien Guerry
2023-08-05  7:12             ` Ihor Radchenko
2023-08-05  8:50               ` Bastien Guerry
2023-08-05 11:06                 ` Ihor Radchenko
2023-08-05 18:07                   ` Bastien Guerry
2023-08-06  6:34                     ` Ihor Radchenko [this message]
2023-08-06 15:17                       ` Bastien Guerry
2023-08-07 13:46                         ` Ihor Radchenko
2023-08-07 14:26                           ` Bastien Guerry
2023-08-10  8:45         ` 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=87350wk7ap.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=news2042@Karl-Voit.at \
    /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).