From: Phil Sainty <psainty@orcon.net.nz>
To: cdelia@dc.uba.ar
Cc: Emacs-devel <emacs-devel-bounces+psainty=orcon.net.nz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: mark .dir-locals.el buffer or file as safe instead of variables as safe
Date: Wed, 27 Jun 2018 16:24:24 +1200 [thread overview]
Message-ID: <037e51edfe70cb450157d1fb6f0ace0d@webmail.orcon.net.nz> (raw)
In-Reply-To: <d0ebecade06de0dcdf602bc66d0fb147@dc.uba.ar>
On 2018-06-27 12:14, cdelia@dc.uba.ar wrote:
> So, if a mark foo-variable, on trusted land to get rid of confirmation
> and just happen to open something on hell itself, by accident or
> glory, instead of a peak of dark magic knowledge I could let all hell
> break lose.
The trust is not for a variable regardless of its value; it is for a
*specific value* of a variable.
If "hell itself" wanted to set the *same* value that was confirmed on
"trusted land" then Emacs will be happy with that; but if a different
value is used then the user will be prompted to confirm (or not) the
new value as trusted.
A variable can be defined to be a "safe-local-variable" such that a
specified predicate function can validate file-local values, and
automatically trust valid values without bothering the user. Otherwise
the user needs to confirm each distinct value independently.
-Phil
next prev parent reply other threads:[~2018-06-27 4:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 0:14 mark .dir-locals.el buffer or file as safe instead of variables as safe cdelia
2018-06-27 2:33 ` Eli Zaretskii
2018-06-27 4:24 ` Phil Sainty [this message]
2018-06-27 4:34 ` Phil Sainty
2018-06-27 6:36 ` Phil Sainty
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=037e51edfe70cb450157d1fb6f0ace0d@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=cdelia@dc.uba.ar \
--cc=emacs-devel-bounces+psainty=orcon.net.nz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.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).