From: "Francesco Potortì" <pot@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 27066@debbugs.gnu.org
Subject: bug#27066: 25.1; dired unsafe variables
Date: Thu, 25 May 2017 17:54:50 +0200 [thread overview]
Message-ID: <E1dDv6A-0003Th-Vp@tucano.isti.cnr.it> (raw)
In-Reply-To: <83k255klmy.fsf@gnu.org>
>> Date: Thu, 25 May 2017 13:57:12 +0200
>> From: Francesco Potortì <pot@gnu.org>
>>
>> Recipe:
>>
>> $ wget http://fly.isti.cnr.it/tmp/leela.tar # 48 MB
>> $ tar -xf leela.tar
>> $ emacs -nw -Q opt/leela
>>
>> I am prompted to accept reading the directory because it contains unsafe
>> variables
>
>I'm not sure why this is deemed a bug: you have a .dir-locals.el file
>in that directory, which specifies directory-local variables. What
>exactly is the problem with the prompt?
I have not created that file myself (downloaded the source code from
Github), and before reading your answer I did not know about the
existence of .dir-locals.el files which get loaded automatically. I
can't find the "dir-local" string anywhere either in the Emacs or Elisp
manuals. Moreover the warning message does not mention .dir-locals.el
anywhere.
So first, there is a documentation problem about the .dir-locals.el
files.
Second, probably dired should prompt *before* ever loading that file and
parse it only if the user agrees. Am I too conservative? Anyway, that
is something that is unespected, and should be treated differently, in
my opinion.
next prev parent reply other threads:[~2017-05-25 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 11:57 bug#27066: 25.1; dired unsafe variables Francesco Potortì
2017-05-25 15:21 ` Eli Zaretskii
2017-05-25 15:54 ` Francesco Potortì [this message]
2017-05-25 16:06 ` Eli Zaretskii
2017-05-25 16:58 ` Francesco Potortì
2017-05-25 18:09 ` Eli Zaretskii
2017-05-25 19:25 ` Francesco Potortì
2022-01-23 16:10 ` Lars Ingebrigtsen
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=E1dDv6A-0003Th-Vp@tucano.isti.cnr.it \
--to=pot@gnu.org \
--cc=27066@debbugs.gnu.org \
--cc=eliz@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).