emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] New remote resource download policy
Date: Tue, 14 Jun 2022 11:40:09 +0200	[thread overview]
Message-ID: <878rpzzipy.fsf@gmail.com> (raw)
In-Reply-To: <87mteiq6ou.fsf@gmail.com> (Timothy's message of "Sun, 12 Jun 2022 22:43:07 +0800")

>>>>> On Sun, 12 Jun 2022 22:43:07 +0800, Timothy <tecosaur@gmail.com> said:

    Timothy> Hi All,
    Timothy> As was raised in the `#+include: URL' thread
    Timothy> (<https://list.orgmode.org/877d5sd7yu.fsf@gmail.com>), currently Org will
    Timothy> automatically download files without confirmation in various circumstances.

    Timothy> This patch introduces two variables to control Org’s attitude towards
    Timothy> downloading files, and hooks them into the relevant parts of the codebase.

I think that would be a good addition. 
    Timothy> +(defcustom org-download-remote-resources 'prompt
    Timothy> +  "The policy applied to requests to obtain remote resources.
    Timothy> +
    Timothy> +This affects keywords like #+setupfile and #+incude on export,
    Timothy> +`org-persist-write:url',and `org-attach-attach' in
    Timothy> +non-interactive Emacs sessions.
    Timothy> +
    Timothy> +This recognises four possible values:
    Timothy> +- t, remote resources should always be downloaded.
    Timothy> +- prompt, you will be prompted to download resources nt considered safe.

'prompted when downloading unsafe resources'


Does this need a 'prompt-always option? I guess thatʼs what you get
with the default value of `org-safe-remote-resources', but maybe it
makes sense to be explicit?


  parent reply	other threads:[~2022-06-14  9:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12 14:43 [PATCH] New remote resource download policy Timothy
2022-06-12 16:18 ` Daniel Fleischer
2022-06-14  9:40 ` Robert Pluim [this message]
2022-06-22  9:58   ` Timothy
2022-06-15 12:35 ` Max Nikulin
2022-06-22 10:01   ` Timothy
2022-06-22 16:55     ` Max Nikulin
2022-06-29 15:27       ` Timothy
2022-06-30 16:57         ` Max Nikulin
2022-07-16  9:47           ` Timothy
2022-06-25  7:50     ` Max Nikulin

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:

  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=878rpzzipy.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@gmail.com \


* 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


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).