emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <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: Sun, 08 Mar 2020 12:52:17 +0000	[thread overview]
Message-ID: <87imjf3t6m.fsf@ucl.ac.uk> (raw)
In-Reply-To: <CAHa53uzmi4rY+RJ6URoEoHpMxsODNsGtup=i4wE0L2kpbOYY7w@mail.gmail.com> (Tim Visher's message of "Fri, 6 Mar 2020 09:09:07 -0500")

On Friday,  6 Mar 2020 at 09:09, Tim Visher wrote:
> I'm less clear on why certain variables are considered safe and some
> are not but that doesn't seem relevant. 

My understanding is that all (most?) variables are considered unsafe
unless you tell emacs otherwise.  I know that my emacs custom variable
include safe-local-variable-values which is a long list of variables
that I have at one time or another told emacs are "safe".

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

  reply	other threads:[~2020-03-08 12:52 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
2020-03-06 14:09   ` Tim Visher
2020-03-08 12:52     ` Eric S Fraga [this message]
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=87imjf3t6m.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).