emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: Tim Visher <tim.visher@gmail.com>
Cc: Emacs Org Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: File Scoped Properties?
Date: Fri, 6 Mar 2020 06:51:27 +0000	[thread overview]
Message-ID: <87mu8ugemp.fsf@ucl.ac.uk> (raw)
In-Reply-To: <CAHa53uznAwwB=N4_8W_2k_A=U=gpyRKzNt9h4oYCiq4LQdm0fg@mail.gmail.com>	(Tim Visher's message of "Thu, 5 Mar 2020 10:28:20 -0500")

On Thursday,  5 Mar 2020 at 10:28, Tim Visher wrote:
> I _am_ able to get it to work by adding a file local variable like
> ```
> # Local Variables:
> # org-attach-id-dir: "~/.foo/data"
> # End:
> ```
> but then whenever I open the file it tells me it's possibly not safe to set
> that.

You've already received a more org-ish response but I'll give you an
Emacs response to this part of your post: Emacs is simply making sure
you are aware that a variable is being set when visiting a file.  It's a
form of security to ensure you don't have a file do something you don't
want it to do.  If you are happy for that variable to be set by files in
this way generally, Emacs does give you the option of saving this
information in the customization file and you won't get asked

It's not that setting this variable this way is dangerous per se.  But,
for instance, this variable could be set by some file you receive from
somebody else to a destination that is off your computer, e.g. using
tramp.  This is the closest that Emacs comes to being vulnerable to
viruses (computer, not COVID-19 ;-)).

: Eric S Fraga via Emacs 28.0.50, Org release_9.3.6-354-g9d5880

  parent reply	other threads:[~2020-03-06  6:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 15:28 File Scoped Properties? Tim Visher
2020-03-05 22:53 ` Gustav Wikström
2020-03-06  6:51 ` Fraga, Eric [this message]
2020-03-06 14:09   ` Tim Visher
2020-03-08 12:52     ` Eric S Fraga
2020-03-09 13:24     ` Tim Visher
2020-03-25  0:57       ` Tim Visher

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=87mu8ugemp.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=tim.visher@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).