From: Leo Butler <Leo.Butler@umanitoba.ca>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Max Nikulin <manikulin@gmail.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Unsolicited download of remote resources
Date: Tue, 6 Feb 2024 16:32:27 +0000 [thread overview]
Message-ID: <87jznh1rl1.fsf@t14.reltub.ca> (raw)
In-Reply-To: <87plxabo5q.fsf@localhost> (Ihor Radchenko's message of "Mon, 05 Feb 2024 21:24:01 +0000")
On Mon, Feb 05 2024, Ihor Radchenko <yantar92@posteo.net> wrote:
> Leo Butler <Leo.Butler@umanitoba.ca> writes:
>
>> Q: if #+setupfile points to a real file available to download, does Org
>> evaluate that file?
>
> keywords and startup options are taken from there. No Elisp code present
> in #+SETUPFILE is evaluated.
>
> That said, if the file defines babel header arguments with elisp or
> "eval" macros, they may be used later, during export or when src block
> evaluation is requested by the user.
So, it is *possible* to have the setupfile set-up arbitrary elisp code
that would be evaluated at some later time (during export or src block
evaluation, as you wrote)? Is that correct?
Leo
next prev parent reply other threads:[~2024-02-06 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 16:57 [BUG] Unsolicited download of remote resources Max Nikulin
2024-02-02 19:04 ` Leo Butler
2024-02-04 12:45 ` Max Nikulin
2024-02-05 19:19 ` Leo Butler
2024-02-05 21:24 ` Ihor Radchenko
2024-02-06 16:32 ` Leo Butler [this message]
2024-02-06 16:49 ` Ihor Radchenko
2024-02-02 20:03 ` Ihor Radchenko
2024-02-04 12:21 ` Max Nikulin
2024-02-04 12:32 ` Ihor Radchenko
2024-02-04 12:56 ` Ihor Radchenko
2024-02-08 10:55 ` Max Nikulin
2024-02-08 15:08 ` 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=87jznh1rl1.fsf@t14.reltub.ca \
--to=leo.butler@umanitoba.ca \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--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).